Triple
T26520880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utah Utes athletic teams |
E669945
|
entity |
| Predicate | homeArenaForGymnastics |
P24374
|
FINISHED |
| Object | Jon M. Huntsman Center |
—
|
NE NERFINISHED |
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: Jon M. Huntsman Center | Statement: [Utah Utes athletic teams, homeArenaForGymnastics, Jon M. Huntsman Center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeArenaForGymnastics Context triple: [Utah Utes athletic teams, homeArenaForGymnastics, Jon M. Huntsman Center]
-
A.
homeVolleyballArena
Indicates that one entity serves as the primary or official volleyball arena or home court for the other entity.
-
B.
homeArenaFor
chosen
Indicates that a particular arena serves as the primary home venue for a specified sports team or organization.
-
C.
homeArenaAlternateName
Indicates that an entity’s home arena is known by an alternate or secondary name.
-
D.
homeArenaType
Indicates the type or category of arena that serves as the primary home venue for an entity.
-
E.
mainIndoorArena
Indicates that one entity serves as the primary indoor arena or main covered venue associated with another entity.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613c22a48819099858ab078b5562f |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:27 a.m.