Triple
T13328452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian Toppserien |
E317502
|
entity |
| Predicate | usesRelegationPlayoff |
P31084
|
FINISHED |
| Object | sometimes |
—
|
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: sometimes | Statement: [Norwegian Toppserien, usesRelegationPlayoff, sometimes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRelegationPlayoff Context triple: [Norwegian Toppserien, usesRelegationPlayoff, sometimes]
-
A.
hasRelegationPlayOff
chosen
Indicates that an entity is involved in or assigned to a relegation play-off match or series to determine its league status.
-
B.
usedForPlayoffQualification
Indicates that something serves as a basis or criterion for determining whether a team qualifies for the playoffs.
-
C.
hasPlayOffs
Indicates that a competition, league, or season includes a playoff stage to determine final rankings or a champion.
-
D.
hasPlayOffsFor
Indicates that an entity organizes or includes playoff competitions specifically for another entity (such as a league, season, or division).
-
E.
hasPlayoffsWith
Indicates that two entities participate together in the same playoff series, bracket, or postseason competition.
- 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6babd88190a5d529df9584b9a4 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:30 p.m.