Triple
T9047261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian football league system |
E216784
|
entity |
| Predicate | domesticCupQualifier |
P18794
|
FINISHED |
| Object | Russian Cup winner |
—
|
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: Russian Cup winner | Statement: [Russian football league system, domesticCupQualifier, Russian Cup winner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domesticCupQualifier Context triple: [Russian football league system, domesticCupQualifier, Russian Cup winner]
-
A.
domesticCupQualifierFor
chosen
Indicates that a team has qualified for participation in a domestic cup competition.
-
B.
domesticCupLevel
Indicates the competitive tier or stage of a team’s participation within a domestic cup competition.
-
C.
domesticCup
Indicates that an entity has won or participated in a domestic (national-level) cup competition within its sport or domain.
-
D.
primaryDomesticCupStatus
Indicates the status or role of a competition as the main domestic cup within a given sports structure or country.
-
E.
hasDomesticCupRelation
Indicates a relationship between entities based on participation, achievement, or involvement in a domestic cup competition within a country’s sports 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_69ca83d362e88190ae44b4e4dc194209 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b5022c88190ab6b6de3c3830a41 |
completed | April 1, 2026, 12:48 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:09 p.m.