Triple
T21675491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Traktor Ice Arena |
E534957
|
entity |
| Predicate | partOfCompetitionSystem |
P13495
|
FINISHED |
| Object | KHL 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: KHL venues | Statement: [Traktor Ice Arena, partOfCompetitionSystem, KHL venues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfCompetitionSystem Context triple: [Traktor Ice Arena, partOfCompetitionSystem, KHL venues]
-
A.
competitionSystem
Indicates the structured set of rules, formats, and procedures that govern how a competition is organized, conducted, and decided.
-
B.
usesCompetitionSystem
chosen
Indicates that an entity operates under or applies a particular competition system or format.
-
C.
associatedWithCompetition
Indicates that there is a relationship or involvement between an entity and a specific competition or competitive event.
-
D.
typeOfCompetition
Indicates the specific kind or category of competition in which an entity participates or is involved.
-
E.
previouslyCompetedAsPartOf
Indicates that an entity once participated in a competition or event as a member or component of another entity, but no longer does so.
- 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_69e0c46898008190aa618a4af55bd1ee |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef8a0f85748190944b9425ffed02ee |
completed | April 27, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:42 p.m.