Triple
T18004595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Professional Football League |
E430712
|
entity |
| Predicate | formerTier |
P85420
|
FINISHED |
| Object | third tier of Russian football |
—
|
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: third tier of Russian football | Statement: [Russian Professional Football League, formerTier, third tier of Russian football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerTier Context triple: [Russian Professional Football League, formerTier, third tier of Russian football]
-
A.
formerGround
Indicates that an entity previously served as the ground or base for another entity but no longer holds that role.
-
B.
formerMaster
Indicates that one entity previously held the role of master over another entity, but no longer does so.
-
C.
formerField
Indicates that an entity previously had a particular field, role, or area of activity, but no longer does.
-
D.
formerDivisionLevel
chosen
Indicates that an entity previously held a certain division level or tier but no longer does so.
-
E.
traditionalTier
Indicates that an entity belongs to, or is categorized within, a conventional or historically established level, class, or rank in a tiered system.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b3eb1f748190904c8894d22cf85f |
completed | April 19, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:23 a.m.