Triple
T2960816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highbury |
E80042
|
entity |
| Predicate | capacityAtClosure |
P14460
|
FINISHED |
| Object | about 38,000 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: about 38,000 | Statement: [Highbury, capacityAtClosure, about 38,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capacityAtClosure Context triple: [Highbury, capacityAtClosure, about 38,000]
-
A.
closureThreshold
Indicates the limit or boundary value at which a process, operation, or state is considered complete or closed.
-
B.
closureFrequency
Indicates how often a particular process, event, or entity is closed or brought to an end within a given period.
-
C.
subjectToClosure
Indicates that an entity is liable or scheduled to be closed, discontinued, or shut down under certain conditions or plans.
-
D.
closureReason
Indicates the reason or cause for which an entity, process, or case has been closed or terminated.
-
E.
maximumCapacity
chosen
Indicates the greatest allowable or designed amount of something that an entity can hold, contain, or handle.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad995454448190834aa5d47a4ed5ac |
completed | March 8, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69ad960c5c8881909d679912bd7d78f3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.