Triple
T16533747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DDR-Oberliga |
E401631
|
entity |
| Predicate | hadChampionshipTitle |
P313
|
FINISHED |
| Object | East German ice hockey champion |
—
|
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: East German ice hockey champion | Statement: [DDR-Oberliga, hadChampionshipTitle, East German ice hockey champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadChampionshipTitle Context triple: [DDR-Oberliga, hadChampionshipTitle, East German ice hockey champion]
-
A.
hasChampionships
chosen
Indicates that one entity possesses or has won one or more championships associated with another entity.
-
B.
championshipTitleWith
Indicates a relationship where two or more entities share or are jointly associated with the same championship title.
-
C.
hasWonRegionalTitle
Indicates that an entity has achieved victory in a competition at the regional level and been awarded the corresponding title.
-
D.
hasWonMultipleChampionships
Indicates that the subject has secured championship titles on more than one separate occasion.
-
E.
hasWorldSeriesTitle
Indicates that an entity (typically a baseball team) has won at least one World Series championship title.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32eda42548190be61efb25a44a554 |
completed | April 18, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.