Triple
T19580009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skagerak Arena |
E489960
|
entity |
| Predicate | partOfLeagueSystem |
P21421
|
FINISHED |
| Object | Eliteserien venues |
—
|
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: Eliteserien venues | Statement: [Skagerak Arena, partOfLeagueSystem, Eliteserien venues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfLeagueSystem Context triple: [Skagerak Arena, partOfLeagueSystem, Eliteserien venues]
-
A.
isPartOfLeague
chosen
Indicates that an entity belongs to, participates in, or is a member of a particular league.
-
B.
hasSeparateLeagueSystemFor
Indicates that one entity organizes or maintains a distinct, independent league structure specifically for another entity or group.
-
C.
typeOfLeagueSystem
Indicates that one entity is the kind or structure of league system to which another entity belongs or in which it operates.
-
D.
countryLeagueSystem
Indicates that a particular league system operates within, or is associated with, a specific country.
-
E.
locatedInLeagueStructure
Indicates that an entity occupies a specific position or level within an organized league’s hierarchical 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6402763b8819099e535979f094f9d |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:42 p.m.