Triple
T23947519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Anzhi Makhachkala |
E602953
|
entity |
| Predicate | peakLeaguePosition |
P51309
|
FINISHED |
| Object | 3rd place in Russian Premier League |
—
|
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: 3rd place in Russian Premier League | Statement: [FC Anzhi Makhachkala, peakLeaguePosition, 3rd place in Russian Premier League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakLeaguePosition Context triple: [FC Anzhi Makhachkala, peakLeaguePosition, 3rd place in Russian Premier League]
-
A.
positionInLeagueSystem
Indicates the rank or tier an entity holds within an organized league or competitive system.
-
B.
clubPosition
Indicates the specific role or position an individual holds within a sports club or team.
-
C.
finalLeaguePosition
chosen
Indicates the finishing rank or place an entity achieved in a league or season-long competition.
-
D.
tourSeasonPosition
Indicates the position or ranking an entity holds within a specific season of a tour or series.
-
E.
positionInLineup
Indicates the specific ordered place an entity occupies within a lineup or sequence of entities.
- 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d02fb4fc8190835baf3bcf909d4d |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:18 p.m.