Triple
T6633916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RSL |
E150396
|
entity |
| Predicate | formerTopTierIn |
P16036
|
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: [RSL, formerTopTierIn, Russian ice hockey league system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerTopTierIn Context triple: [RSL, formerTopTierIn, Russian ice hockey league system]
-
A.
firstTier
Indicates that one entity occupies the highest or primary level, rank, or priority relative to others in a hierarchical structure.
-
B.
topTierUntil
Indicates that an entity holds a top-tier or highest-status position only up to a specified point in time, after which this status no longer applies.
-
C.
formerHighest
chosen
Indicates that an entity once held the highest rank, position, or status in a given context but no longer does.
-
D.
topTierRelation
Indicates a relationship in which one entity belongs to the highest or most elite level within a ranked or hierarchical set of entities.
-
E.
formsTopOf
Indicates that one entity constitutes the uppermost part or surface of another entity.
- 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_69c687f0ceb08190bf40807bfc605fa5 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c308a08881908501c862b3029321 |
completed | March 27, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c6ad024860819084b9b535b136ede6 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:59 p.m.