Triple
T16533753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DDR-Oberliga |
E401631
|
entity |
| Predicate | wasAbove |
P123936
|
FINISHED |
| Object | lower-tier East German ice hockey leagues |
—
|
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: lower-tier East German ice hockey leagues | Statement: [DDR-Oberliga, wasAbove, lower-tier East German ice hockey leagues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasAbove Context triple: [DDR-Oberliga, wasAbove, lower-tier East German ice hockey leagues]
-
A.
above
Indicates that one entity is positioned higher than another along a vertical axis, without implying direct contact.
-
B.
wasA
Indicates that an entity previously had a certain role, type, or classification in the past.
-
C.
wasIn
Indicates that an entity existed, occurred, or was located within a particular place or context during a specified time or situation.
-
D.
over
Indicates that one entity is positioned higher than and extending across or above another entity, often covering or spanning it.
-
E.
raisedTo
Indicates that one entity has been elevated, lifted, or brought up to a higher level, position, or state by another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:15 a.m.