Triple
T28985101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basketligan |
E734657
|
entity |
| Predicate | previousTopDivisionName |
P54355
|
FINISHED |
| Object | Elitserien i basket |
—
|
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: Elitserien i basket | Statement: [Basketligan, previousTopDivisionName, Elitserien i basket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousTopDivisionName Context triple: [Basketligan, previousTopDivisionName, Elitserien i basket]
-
A.
previousTopDivisionOf
Indicates that an entity was formerly in the highest-level division or tier of a given organizational or competitive structure.
-
B.
historicalTopDivisionName
chosen
Indicates that an entity had a particular name for its top competitive division during a past period in its history.
-
C.
replacedAsTopDivisionBy
Indicates that one top-level division or league has been superseded and taken over in status or role by another.
-
D.
topDivision
Indicates that an entity belongs to the highest-level division or tier within a hierarchical structure.
-
E.
topDivisionLevel
Indicates that an entity belongs to the highest or primary division level within a hierarchical or organizational structure.
- 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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: April 28, 2026, 9:13 a.m.