Triple
T20556357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munich derby |
E504729
|
entity |
| Predicate | associatedWithStadiumShare |
P1749
|
FINISHED |
| Object | Allianz Arena shared history |
—
|
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: Allianz Arena shared history | Statement: [Munich derby, associatedWithStadiumShare, Allianz Arena shared history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithStadiumShare Context triple: [Munich derby, associatedWithStadiumShare, Allianz Arena shared history]
-
A.
associatedWithStadiumLocation
Indicates a relationship where an entity is connected or linked to the location of a specific stadium.
-
B.
sharesStadiumWith
chosen
Indicates that two teams or organizations use the same stadium as their home or primary venue.
-
C.
associatedStadiums
Indicates that there is a relationship linking an entity to one or more stadiums with which it is connected or affiliated.
-
D.
stadiumOwner
Indicates that one entity owns or holds legal possession of a stadium associated with another entity.
-
E.
sharedStadiumRegion
Indicates that two or more entities use stadiums located within the same geographic region.
- 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_69e0b4b6587c8190aee63dc7cff244ea |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a5de9c008190b8620628fb285e90 |
completed | April 20, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:38 a.m.