Triple
T31870592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordtribüne |
E813585
|
entity |
| Predicate | hasRelativePositionInStadium |
—
|
GENERATED |
| Object | behind one of the goals |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
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 (1 batch)
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. |
Created at: April 30, 2026, 11:54 p.m.