Triple
T3678408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empower Field at Mile High |
E78050
|
entity |
| Predicate | usedForEventType |
P29202
|
FINISHED |
| Object | NFL games |
—
|
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: NFL games | Statement: [Empower Field at Mile High, usedForEventType, NFL games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForEventType Context triple: [Empower Field at Mile High, usedForEventType, NFL games]
-
A.
eventUse
Indicates that an event involves the use or utilization of a particular entity (e.g., a resource, tool, or method) as part of its occurrence.
-
B.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
C.
hasEventType
Indicates that an event is associated with, or classified under, a specific type or category of event.
-
D.
eventUsage
Indicates how an event is employed, applied, or utilized within a particular context or process.
-
E.
servesEventType
chosen
Indicates that an entity provides or supports a particular type or category of event.
- 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.