Triple
T31812744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Südtribüne |
E812049
|
entity |
| Predicate | stadiumSectionOf |
P172919
|
FINISHED |
| Object | Millerntor-Stadion |
—
|
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: Millerntor-Stadion | Statement: [Südtribüne, stadiumSectionOf, Millerntor-Stadion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stadiumSectionOf Context triple: [Südtribüne, stadiumSectionOf, Millerntor-Stadion]
-
A.
usesStadiumSectionFor
Indicates that a particular stadium section is utilized for a specific purpose, activity, or function.
-
B.
stadiumSectionReputation
Indicates the perceived quality or notoriety associated with a particular section of a stadium, based on factors like fan behavior, atmosphere, or safety.
-
C.
hasSeatingSections
Indicates that an entity is divided into distinct seating areas or sections designated for occupants.
-
D.
hasAwaySupportersSection
Indicates that a venue or stadium includes a designated seating area specifically reserved for supporters of the visiting team.
-
E.
fanSectionLocation
Indicates the specific area or section within a venue where a fan or group of fans is located.
- F. None of above. chosen
Provenance (4 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 30, 2026, 11:44 p.m.