Triple
T8306380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Husky Stadium |
E194472
|
entity |
| Predicate | hasUpperDecks |
P82659
|
FINISHED |
| Object | cantilevered metal roofs |
—
|
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: cantilevered metal roofs | Statement: [Husky Stadium, hasUpperDecks, cantilevered metal roofs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpperDecks Context triple: [Husky Stadium, hasUpperDecks, cantilevered metal roofs]
-
A.
hasLowerDeckFunction
Indicates that an entity serves a specific role or performs a designated function on the lower deck of a structure or vehicle.
-
B.
hasUpperFloor
Indicates that one entity possesses or includes an upper floor relative to another level or reference point.
-
C.
upperDeckDirection
Indicates the direction or orientation associated with the upper deck relative to a reference point or structure.
-
D.
upperDeckUsedFor
Indicates that the upper deck of an object or structure is utilized for a specified purpose or activity.
-
E.
hasUpperFloorUse
Indicates that an entity’s upper floor is assigned or designated for a particular use or function.
- 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f293db08190912e5e8bb7e940cf |
completed | March 31, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:54 p.m.