Triple
T31812739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Südtribüne |
E812049
|
entity |
| Predicate | ticketTypeCommon |
P172918
|
FINISHED |
| Object | standing tickets |
—
|
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: standing tickets | Statement: [Südtribüne, ticketTypeCommon, standing tickets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketTypeCommon Context triple: [Südtribüne, ticketTypeCommon, standing tickets]
-
A.
ticketTypeExample
Indicates that an entity serves as an example or illustrative instance of a particular ticket type.
-
B.
ticketTypeStored
Indicates that a particular type of ticket has been recorded and saved in a storage or system.
-
C.
ticketTypeAccepted
Indicates that a particular type of ticket is valid for use or accepted in a given context or by a given entity.
-
D.
ticketFormat
Indicates the specific structure, layout, or template in which a ticket is represented or issued.
-
E.
ticketGatesType
Indicates the type or category of ticket gates associated with a given entity or location.
- 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.