Triple
T9573396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EnergySolutions Arena |
E230982
|
entity |
| Predicate | usedAsHomeArenaFrom |
P89880
|
FINISHED |
| Object | 1991 |
—
|
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: 1991 | Statement: [EnergySolutions Arena, usedAsHomeArenaFrom, 1991]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsHomeArenaFrom Context triple: [EnergySolutions Arena, usedAsHomeArenaFrom, 1991]
-
A.
formerHomeArena
Indicates that a venue previously served as the primary home arena for a team or organization but no longer holds that status.
-
B.
usedAsHomeCourtOf
Indicates that a particular venue or location serves as the primary home court where a team or individual regularly hosts its games or matches.
-
C.
formerHomeStadium
Indicates that a venue previously served as the home stadium for a team or organization but no longer holds that status.
-
D.
homeArenaAlternateName
Indicates that an entity’s home arena is known by an alternate or secondary name.
-
E.
formerHomeVenue
Indicates that a location previously served as the primary venue or home ground for an entity, but no longer holds that status.
- 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_69ca848091c48190bc313d6620d09555 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd998d79cc8190b94e5953915a5fa4 |
completed | April 1, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69ccd59b960c8190966a8870a2426bd5 |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93e90048190a2b0d7c5c195ba98 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:04 p.m.