Triple
T37923069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Das Wunder von Bern |
E946015
|
entity |
| Predicate | locationOfFinalMatchDepicted |
P115926
|
FINISHED |
| Object | Wankdorf Stadium |
E280026
|
NE 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: Wankdorf Stadium | Statement: [Das Wunder von Bern, locationOfFinalMatchDepicted, Wankdorf Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfFinalMatchDepicted Context triple: [Das Wunder von Bern, locationOfFinalMatchDepicted, Wankdorf Stadium]
-
A.
finalsLocation
Indicates the place where the final stage or concluding event of something (such as a competition or process) takes place.
-
B.
venueOfFinalMatch
chosen
Indicates the location where the final match of a competition or tournament is held.
-
C.
finalManOfTheMatch
Indicates that the referenced person was chosen as the ultimate or concluding Man of the Match for a particular game or series.
-
D.
finalMatchCity
Indicates the city where the final match of a competition or tournament takes place.
-
E.
formerFinishLocation
Indicates that an entity was previously the finish location of an event or activity, but no longer holds that status.
- F. None of above.
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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a410cd4bf748190be299c50e2a80c75 |
completed | June 28, 2026, noon |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.