Triple
T13961666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IIHF competitions |
E335807
|
entity |
| Predicate | divisionSystem |
P18043
|
FINISHED |
| Object | tiered |
—
|
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: tiered | Statement: [IIHF competitions, divisionSystem, tiered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionSystem Context triple: [IIHF competitions, divisionSystem, tiered]
-
A.
usesDivisionSystem
chosen
Indicates that one entity organizes or structures something by applying a particular system of division or categorization.
-
B.
divisionFormat
Indicates the specific structural or organizational format in which a division or subdivision is arranged or presented.
-
C.
numberingSystemBasedOn
Indicates that one numbering system is derived from, structured according to, or conceptually dependent on another numbering system.
-
D.
denominationSystem
Indicates a relationship where one entity defines, uses, or belongs to a particular system of denominations (such as units, values, or classifications) established by another entity.
-
E.
notationSystem
Indicates a relationship where one entity is the system or method of notation used to represent or encode 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e7c73d48190b8e02971b5a8ed5f |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69de05a3ccf88190b45c742db483fa08 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:18 p.m.