Triple
T29727533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gegengerade (Max-Morlock-Stadion) |
E752223
|
entity |
| Predicate | belongsToStadiumType |
P194989
|
FINISHED |
| Object | multi-purpose stadium |
—
|
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: multi-purpose stadium | Statement: [Gegengerade (Max-Morlock-Stadion), belongsToStadiumType, multi-purpose stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToStadiumType Context triple: [Gegengerade (Max-Morlock-Stadion), belongsToStadiumType, multi-purpose stadium]
-
A.
appliedToStadiumType
Indicates that something (such as a rule, condition, or attribute) is specifically applied to a particular type or category of stadium.
-
B.
hostStadiumType
Indicates the type or category of stadium that serves as the host venue for an event or activity.
-
C.
containsStadium
Indicates that a location or area includes a stadium within its boundaries or premises.
-
D.
homeStadiumType
Indicates the type or classification of a venue that serves as a team's primary home stadium.
-
E.
associatedWithStadiumLocation
Indicates a relationship where an entity is connected or linked to the location of a specific stadium.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69fd974c0e8481909fdd312897c647b3 |
completed | May 8, 2026, 7:57 a.m. |
Created at: April 28, 2026, 7:40 p.m.