Triple
T1317923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gagarin Cup |
E28147
|
entity |
| Predicate | associatedCompetitionLevel |
P18266
|
FINISHED |
| Object | top-tier professional |
—
|
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: top-tier professional | Statement: [Gagarin Cup, associatedCompetitionLevel, top-tier professional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCompetitionLevel Context triple: [Gagarin Cup, associatedCompetitionLevel, top-tier professional]
-
A.
associatedWithCompetition
Indicates that there is a relationship or involvement between an entity and a specific competition or competitive event.
-
B.
hasRelatedCompetition
Indicates that one competition is related to another competition in a meaningful way, such as being similar, connected, or associated within a shared context.
-
C.
primaryCompetitionLevel
chosen
Indicates the main or highest level of competition at which an entity primarily competes or operates.
-
D.
competitionLevel
Indicates the degree or intensity of competitive pressure or rivalry present in a given context or interaction.
-
E.
levelOfCompetition
Indicates the intensity or degree of competitive pressure present in a given context or interaction.
- 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_69a498532c3481909223b74af2e578df |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c176c89881909e9dc0e34f12f056 |
completed | March 1, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69a4beebcb348190964bd7215811942c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.