Triple
T1317977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Superleague |
E28148
|
entity |
| Predicate | topLevelInSystem |
P7559
|
FINISHED |
| Object | Russian ice hockey league system |
—
|
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: Russian ice hockey league system | Statement: [Russian Superleague, topLevelInSystem, Russian ice hockey league system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topLevelInSystem Context triple: [Russian Superleague, topLevelInSystem, Russian ice hockey league system]
-
A.
topLevelOf
Indicates that one entity is the highest or most overarching level within the structure or hierarchy of another entity.
-
B.
hasTopLevel
Indicates that one entity is the highest or primary element within a hierarchy or structure relative to another entity.
-
C.
titleSystem
Indicates that a system assigns or holds a formal title or designation for an entity.
-
D.
isTopLevelLeagueIn
chosen
Indicates that a sports league is the highest (top-tier) competitive level within a specified country or region.
-
E.
isFirstLineOfSystem
Indicates that one entity is the initial or starting line within a defined system or system representation.
- 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_69a498532c3481909223b74af2e578df |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c176c89881909e9dc0e34f12f056 |
completed | March 1, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69a4beebcb348190964bd7215811942c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.