Triple
T3678389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empower Field at Mile High |
E78050
|
entity |
| Predicate | capacityAmericanFootball |
P13599
|
FINISHED |
| Object | approximately 76,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: approximately 76,000 | Statement: [Empower Field at Mile High, capacityAmericanFootball, approximately 76,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capacityAmericanFootball Context triple: [Empower Field at Mile High, capacityAmericanFootball, approximately 76,000]
-
A.
stadiumCapacityApprox
chosen
Indicates an approximate number of people that a stadium can accommodate.
-
B.
stadiumCapacityContext
Indicates the seating capacity of a stadium as it applies within a specific contextual scope (such as time, event, or configuration).
-
C.
homeStadiumCapacity
Indicates the seating capacity of the stadium that serves as a team's or organization's home venue.
-
D.
capacityBaseball
Indicates the maximum number of spectators that a baseball venue is designed or allowed to hold.
-
E.
capacityCategory
Indicates the classification of something based on the amount or volume it can hold, handle, or accommodate.
- 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_69ad85e18c1c8190be8aafb227f39f48 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc46599188190a046eddb0d85c483 |
completed | March 8, 2026, 6:48 p.m. |
| PD | Predicate disambiguation | batch_69adb84be1fc81909721c871babb4633 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.