Triple
T31870592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordtribüne |
E813585
|
entity |
| Predicate | hasRelativePositionInStadium |
P95425
|
FINISHED |
| Object | behind one of the goals |
—
|
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: behind one of the goals | Statement: [Nordtribüne, hasRelativePositionInStadium, behind one of the goals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelativePositionInStadium Context triple: [Nordtribüne, hasRelativePositionInStadium, behind one of the goals]
-
A.
relativePositionInStadium
chosen
Indicates the spatial relationship between entities based on where they are located relative to each other within a stadium.
-
B.
roleAtStadium
Indicates that an entity holds a specific role, function, or position associated with a particular stadium.
-
C.
locatedInStadium
Indicates that an entity is situated within or at the premises of a specific stadium.
-
D.
relativePositionWithinTeam
Indicates the positional or hierarchical relationship an entity holds relative to other members within the same team.
-
E.
hasNearbyStadium
Indicates that one entity is located close to or in the vicinity of a stadium associated with another entity.
- 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_6a01ade363088190b3a3e3dedabd1aa2 |
completed | May 11, 2026, 10:22 a.m. |
| PD | Predicate disambiguation | batch_6a01acf3c5788190932bd8fcf27c123d |
completed | May 11, 2026, 10:18 a.m. |
Created at: April 30, 2026, 11:54 p.m.