Triple
T26461679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AT |
E665654
|
entity |
| Predicate | usedOnCompetitionLevel |
P161298
|
FINISHED |
| Object | World Championship level |
—
|
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: World Championship level | Statement: [AT, usedOnCompetitionLevel, World Championship level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedOnCompetitionLevel Context triple: [AT, usedOnCompetitionLevel, World Championship level]
-
A.
usedInCompetition
Indicates that something is employed or utilized as part of a competition or contest.
-
B.
usesCompetition
Indicates that one entity employs or leverages another entity as a competitor or within a competitive context.
-
C.
usedInCompetitionContext
Indicates that something is employed or occurs within the setting, rules, or circumstances of a competition or contest.
-
D.
usesCompetitionSystem
Indicates that an entity operates under or applies a particular competition system or format.
-
E.
appliesToCompetition
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable specifically to a competition.
- F. None of above. chosen
Provenance (4 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f6125e54e0819088ee33a20efcc9e6 |
completed | May 2, 2026, 3:03 p.m. |
Created at: April 27, 2026, 12:13 a.m.