Triple
T5631035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northumberland Development Project |
E147830
|
entity |
| Predicate | formerStadiumCapacityApprox |
P64680
|
FINISHED |
| Object | 36000 |
—
|
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: 36000 | Statement: [Northumberland Development Project, formerStadiumCapacityApprox, 36000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerStadiumCapacityApprox Context triple: [Northumberland Development Project, formerStadiumCapacityApprox, 36000]
-
A.
stadiumCapacityApprox
Indicates an approximate number of people that a stadium can accommodate.
-
B.
homeStadiumCapacity
Indicates the seating capacity of the stadium that serves as a team's or organization's home venue.
-
C.
stadiumCapacityContext
Indicates the seating capacity of a stadium as it applies within a specific contextual scope (such as time, event, or configuration).
-
D.
formerStadiumClosed
Indicates that a stadium, which previously served as the home venue for an entity, has been permanently closed.
-
E.
hostStadiumPreviousName
Indicates that a stadium previously had a different official name before its current one.
- F. None of above. chosen
Provenance (4 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0225cdcdc819095034f12c39ef755 |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0684908190ae2d14f0bd2ab892 |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:40 p.m.