Triple
T26564694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hockeyettan |
E666343
|
entity |
| Predicate | usesRelegationRound |
P80426
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hockeyettan, usesRelegationRound, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRelegationRound Context triple: [Hockeyettan, usesRelegationRound, yes]
-
A.
hasRelegationTo
Indicates that an entity is demoted or moved down to a lower level, tier, or division within a hierarchical system.
-
B.
reachedRound
Indicates that an entity has advanced to or attained a particular round or stage within a process, event, or competition.
-
C.
hasRound
Indicates that an entity possesses, includes, or is associated with a particular round (e.g., a round of an event, game, or process).
-
D.
hasRelegationSpots
Indicates that a competition or league includes designated positions in its standings whose occupants will be relegated to a lower division or tier.
-
E.
relegationRound
chosen
Indicates that entities are involved in a stage or match of a competition where participants risk being demoted to a lower division or tier.
- 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_69ee9cf7e94481909f0d556b36e43572 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:54 a.m.