Triple
T27413976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lokomotiv Moscow |
E692838
|
entity |
| Predicate | competesInSeasonalLeague |
P54920
|
FINISHED |
| Object | Russian Premier League |
—
|
NE NERFINISHED |
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 Premier League | Statement: [Lokomotiv Moscow, competesInSeasonalLeague, Russian Premier League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competesInSeasonalLeague Context triple: [Lokomotiv Moscow, competesInSeasonalLeague, Russian Premier League]
-
A.
competesInSeasonalFormat
chosen
Indicates that an entity participates in a competition that is organized into recurring seasons or seasonal formats.
-
B.
hasSeasonalParticipationIn
Indicates that an entity takes part in or is involved with another entity only during specific seasons or recurring seasonal periods.
-
C.
joinedLeagueInSeason
Indicates that an entity became a member of a particular league starting in a specified season.
-
D.
competitionSeason
Indicates that an entity is associated with a particular competitive season or edition of a competition.
-
E.
hasSeasonType
Indicates that something is associated with a particular category or type of season (e.g., summer, winter, rainy).
- 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_69ef5208617081908f731d312e0fd1bc |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 12:33 p.m.