Triple
T21729494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utah State Aggies men's basketball |
E536366
|
entity |
| Predicate | homeCourtAtmosphere |
P52849
|
FINISHED |
| Object | strong |
—
|
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: strong | Statement: [Utah State Aggies men's basketball, homeCourtAtmosphere, strong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeCourtAtmosphere Context triple: [Utah State Aggies men's basketball, homeCourtAtmosphere, strong]
-
A.
homeGameAtmosphere
chosen
Indicates the overall mood, energy, and environmental conditions experienced by participants and spectators during a team's home game.
-
B.
homeCourtDedicatedTo
Indicates that a particular sports venue or court is officially named for or ceremonially assigned in honor of a specific person, group, or entity.
-
C.
homeCourtAdvantageFor
Indicates that one party benefits from playing or competing on its own familiar venue or territory against another party.
-
D.
homeArenaType
Indicates the type or category of arena that serves as the primary home venue for an entity.
-
E.
homeArenaAlternateName
Indicates that an entity’s home arena is known by an alternate or secondary name.
- 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_69e0c46d3284819099a4f9d5a704eb95 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69effd04c9648190922e8fa7c74ac1b5 |
completed | April 28, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:48 p.m.