Triple
T9573413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EnergySolutions Arena |
E230982
|
entity |
| Predicate | hasEventFloorConfiguration |
P70381
|
FINISHED |
| Object | basketball configuration |
—
|
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: basketball configuration | Statement: [EnergySolutions Arena, hasEventFloorConfiguration, basketball configuration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEventFloorConfiguration Context triple: [EnergySolutions Arena, hasEventFloorConfiguration, basketball configuration]
-
A.
hasFloor
Indicates that one entity possesses, includes, or is associated with a particular floor or level within a structure.
-
B.
hasDanceFloor
Indicates that a place or venue includes a designated area intended for dancing.
-
C.
hasFloorUse
Indicates that a particular floor or level of a building is designated for a specific function, activity, or type of use.
-
D.
floorAssociatedWithEvent
chosen
Indicates that a particular floor is related or linked to a specific event, such as being its location or venue.
-
E.
hasTradingFloor
Indicates that an entity operates or contains a physical or virtual trading floor where financial instruments are actively bought and sold.
- 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.