Triple
T29727500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordkurve |
E752222
|
entity |
| Predicate | stadiumSectionOrientation |
P137225
|
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: [Nordkurve, stadiumSectionOrientation, north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stadiumSectionOrientation Context triple: [Nordkurve, stadiumSectionOrientation, north]
-
A.
stadiumOrientation
Indicates the directional alignment or layout of a stadium relative to a reference (e.g., compass directions or surrounding features).
-
B.
usesStadiumSectionFor
Indicates that a particular stadium section is utilized for a specific purpose, activity, or function.
-
C.
hasSeatingSections
Indicates that an entity is divided into distinct seating areas or sections designated for occupants.
-
D.
seatingDirection
chosen
Indicates the orientation or facing direction in which an entity is seated relative to a reference point or object.
-
E.
stadiumSectionReputation
Indicates the perceived quality or notoriety associated with a particular section of a stadium, based on factors like fan behavior, atmosphere, or safety.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f673008bb081909623ca50205dc0a8 |
completed | May 2, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:40 p.m.