Triple
T27474817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Die Schwaben |
E693426
|
entity |
| Predicate | associatedWithStadiumFormerName |
P194309
|
FINISHED |
| Object | Mercedes-Benz Arena |
—
|
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: Mercedes-Benz Arena | Statement: [Die Schwaben, associatedWithStadiumFormerName, Mercedes-Benz Arena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithStadiumFormerName Context triple: [Die Schwaben, associatedWithStadiumFormerName, Mercedes-Benz Arena]
-
A.
associatedWithStadiumNameHistory
Indicates that there is a relationship between an entity and the historical or past names of a stadium with which it has been associated.
-
B.
associatedWithStadiumNickname
Indicates that an entity is connected to or commonly referred to by a particular stadium nickname.
-
C.
previousNameOfStadiumOfClub
chosen
Indicates that one entity is a former name previously used for the stadium belonging to a particular sports club.
-
D.
stadiumAlsoKnownAs
Indicates that a stadium has an alternative name or alias by which it is also known.
-
E.
associatedWithStadiumLocation
Indicates a relationship where an entity is connected or linked to the location of a specific stadium.
- 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_69ef5381f2648190a2392d0fab833095 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fff9b126b4819085a4cf8791d388d1 |
completed | May 10, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69fff8f913a881908d3b7e490d92631f |
completed | May 10, 2026, 3:18 a.m. |
Created at: April 27, 2026, 12:56 p.m.