Triple
T9573390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EnergySolutions Arena |
E230982
|
entity |
| Predicate | hasNBAFloor |
P5519
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [EnergySolutions Arena, hasNBAFloor, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNBAFloor Context triple: [EnergySolutions Arena, hasNBAFloor, yes]
-
A.
hasBasketballLevel
Indicates that an entity possesses a specified level of skill, proficiency, or ranking in basketball.
-
B.
hasFloor
chosen
Indicates that one entity possesses, includes, or is associated with a particular floor or level within a structure.
-
C.
usesStandardBasketballCourt
Indicates that the subject conducts its basketball-related activities on a regulation-size, standard-layout basketball court.
-
D.
playedInNBA
Indicates that the subject has participated as a player in at least one official National Basketball Association (NBA) game.
-
E.
hasNBAFranchiseHistoryFrom
Indicates that an entity has a history of operating an NBA franchise originating from a specified location or organization.
- 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_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. |
Created at: March 30, 2026, 8:04 p.m.