Triple
T10710218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TCF Bank Stadium |
E252512
|
entity |
| Predicate | hasVideoBoardLocation |
P16010
|
FINISHED |
| Object | west end zone |
—
|
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: west end zone | Statement: [TCF Bank Stadium, hasVideoBoardLocation, west end zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVideoBoardLocation Context triple: [TCF Bank Stadium, hasVideoBoardLocation, west end zone]
-
A.
hasVideoBoard
chosen
Indicates that an entity is equipped with or includes a video board (graphics/display hardware component).
-
B.
hasLocalBoards
Indicates that an entity is associated with one or more governing or administrative boards operating at a local or regional level.
-
C.
onboardLocation
Indicates that one entity is located on or within a vehicle, vessel, or other conveyance associated with another entity.
-
D.
hasServiceBoard
Indicates that an entity is associated with or connected to a specific service board, such as a panel or group responsible for providing or overseeing services.
-
E.
hasBoardType
Indicates that an entity is associated with or uses a specific type or category of board.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fe515b1081909532a20b61ff6cf0 |
completed | April 9, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69d6f30455888190b77f476b8418eaee |
completed | April 9, 2026, 12:29 a.m. |
Created at: April 8, 2026, 9:13 p.m.