Triple
T7262120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Premier League |
E159679
|
entity |
| Predicate | hasUEFACoefficientRanking |
P76001
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Russian Premier League, hasUEFACoefficientRanking, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUEFACoefficientRanking Context triple: [Russian Premier League, hasUEFACoefficientRanking, yes]
-
A.
fifaLikeRankingType
Indicates a ranking system or classification that follows the style, rules, or methodology of FIFA’s official rankings.
-
B.
hasUEFACategory
Indicates that an entity is classified under a specific UEFA-defined category or tier.
-
C.
levelInUEFASystem
Indicates the specific tier or division an entity occupies within the hierarchical structure of the UEFA football league system.
-
D.
hasRankingUnit
Indicates that one entity is associated with a specific unit or scale used to express its ranking or ordered position.
-
E.
usedInFIFAWorldRankingLists
Indicates that something (typically a system, method, or data) is employed as part of the process for creating or determining the official FIFA World Ranking lists.
- 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_69c68838f9948190875fd60b2351230c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb088dac8190b353f6ea3d686025 |
completed | March 27, 2026, 8:39 p.m. |
| PD | Predicate disambiguation | batch_69c6e76876608190ac4652bc7153302e |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6eb06acd881908a1735fbbbd5756f |
completed | March 27, 2026, 8:39 p.m. |
Created at: March 27, 2026, 2:57 p.m.