Triple
T38057172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bruchwegstadion |
E950235
|
entity |
| Predicate | hasSeatingAndStandingAreas |
P34773
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Bruchwegstadion, hasSeatingAndStandingAreas, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeatingAndStandingAreas Context triple: [Bruchwegstadion, hasSeatingAndStandingAreas, yes]
-
A.
hasSeatingCapacityWithStanding
Indicates that an entity has a total seating capacity that explicitly includes standing room capacity as part of its overall accommodation.
-
B.
hasStandingArea
chosen
Indicates that an entity includes or provides a designated area where people can stand.
-
C.
hasSafeStandingAreas
Indicates that designated locations within an area provide secure, stable, and protected spots where individuals can safely stand.
-
D.
hasSeating
Indicates that one entity provides or contains seating capacity or seating arrangements for another entity.
-
E.
hasAllSeaterStands
Indicates that all stands or spectator areas associated with an entity consist entirely of seated accommodations, with no standing-only sections.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00b6e163308190adeb1d6eb8558641 |
completed | May 10, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_6a00b67e0e388190b08ad66cee4cb0d7 |
completed | May 10, 2026, 4:46 p.m. |
Created at: May 3, 2026, 4:21 p.m.