Triple
T28845285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Stand |
E728435
|
entity |
| Predicate | locationOnSideOf |
P31095
|
FINISHED |
| Object | Reebok Stadium |
—
|
NE NERFINISHED |
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: Reebok Stadium | Statement: [East Stand, locationOnSideOf, Reebok Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOnSideOf Context triple: [East Stand, locationOnSideOf, Reebok Stadium]
-
A.
locationSide
Indicates that one entity is positioned on a particular side (e.g., left, right, front, back) relative to another entity or reference point.
-
B.
situatedOnSideOf
chosen
Indicates that one entity is located along or beside the lateral part or edge of another entity.
-
C.
locationOnSquare
Indicates that one entity is positioned on a specific square region or cell within a larger spatial grid or board.
-
D.
locatedAlong
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
-
E.
leftLocation
Indicates that an entity has departed from or moved away from a specified location.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69ffc1550cb481908628e446d9b67f7b |
completed | May 9, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69ffc10a74708190ae90e2c378791f70 |
completed | May 9, 2026, 11:19 p.m. |
Created at: April 28, 2026, 6:42 a.m.