Triple
T32181077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boris Gelfand |
E821982
|
entity |
| Predicate | worldChampionshipChallenger |
P195000
|
FINISHED |
| Object | Viswanathan Anand |
—
|
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: Viswanathan Anand | Statement: [Boris Gelfand, worldChampionshipChallenger, Viswanathan Anand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldChampionshipChallenger Context triple: [Boris Gelfand, worldChampionshipChallenger, Viswanathan Anand]
-
A.
worldChampionshipsOrganiser
Indicates that the subject is responsible for organizing or managing world championship events for the object.
-
B.
worldChampionIn
Indicates that an entity holds or has held the title of world champion in a specified field, discipline, or competition.
-
C.
featuredWorldChampion
Indicates that an entity has been highlighted or showcased specifically in its capacity as a world champion.
-
D.
featuredChallenger
Indicates that an entity is highlighted or designated as a primary or special challenger in a given context or competition.
-
E.
challengerClub
Indicates that one club is the challenger or opposing club in a competitive context relative to another entity.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69fd974c0e8481909fdd312897c647b3 |
completed | May 8, 2026, 7:57 a.m. |
Created at: May 1, 2026, 12:34 a.m.