Triple
T27413966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lokomotiv Moscow |
E692838
|
entity |
| Predicate | clubNameInRussian |
P162655
|
FINISHED |
| Object | Футбольный клуб «Локомотив» Москва |
—
|
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: Футбольный клуб «Локомотив» Москва | Statement: [Lokomotiv Moscow, clubNameInRussian, Футбольный клуб «Локомотив» Москва]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clubNameInRussian Context triple: [Lokomotiv Moscow, clubNameInRussian, Футбольный клуб «Локомотив» Москва]
-
A.
clubNameInArabic
Indicates the name of a club as written or expressed in the Arabic language.
-
B.
clubNameInSwedish
Indicates that the predicate specifies the name of a club as expressed in the Swedish language.
-
C.
alternativeNameOfClub
Indicates that one club is an alternative or secondary name/designation for another club.
-
D.
clubFullName
Indicates the complete official name of a club as opposed to an abbreviation or short form.
-
E.
associatedClubCommonName
Indicates that there is a relationship linking an entity to the commonly used or popular name of a club with which it is associated.
- 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_69ef5208617081908f731d312e0fd1bc |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62cd1912c8190ab3f3288442115a4 |
completed | May 2, 2026, 4:56 p.m. |
Created at: April 27, 2026, 12:33 p.m.