Triple
T31870561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordtribüne |
E813585
|
entity |
| Predicate | directionRelativeToStadiumCenter |
P95425
|
FINISHED |
| Object | north |
—
|
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: north | Statement: [Nordtribüne, directionRelativeToStadiumCenter, north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionRelativeToStadiumCenter Context triple: [Nordtribüne, directionRelativeToStadiumCenter, north]
-
A.
relativePositionInStadium
chosen
Indicates the spatial relationship between entities based on where they are located relative to each other within a stadium.
-
B.
stadiumOrientation
Indicates the directional alignment or layout of a stadium relative to a reference (e.g., compass directions or surrounding features).
-
C.
directionFromParkCenter
Indicates the compass direction or relative bearing of an entity when measured outward from the center point of a park.
-
D.
stadiumFor
Indicates that a particular stadium serves as the designated home or primary venue for a specific team, event, or organization.
-
E.
distanceToCenterField
Indicates the measured distance from a given point or object to the center of a designated field or playing area.
- 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: April 30, 2026, 11:54 p.m.