Triple
T34873621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Chess Championship 2006 |
E1005818
|
entity |
| Predicate | FIDEWorldChampionBeforeMatch |
P181957
|
FINISHED |
| Object | Veselin Topalov |
—
|
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: Veselin Topalov | Statement: [World Chess Championship 2006, FIDEWorldChampionBeforeMatch, Veselin Topalov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FIDEWorldChampionBeforeMatch Context triple: [World Chess Championship 2006, FIDEWorldChampionBeforeMatch, Veselin Topalov]
-
A.
featuredWorldChampion
Indicates that an entity has been highlighted or showcased specifically in its capacity as a world champion.
-
B.
FIDEtitle
Indicates that an entity holds a specific official chess title as recognized by FIDE (the International Chess Federation).
-
C.
FIDEWorldRanking
Indicates that an entity holds a specific position in the official FIDE world chess rankings at a given time.
-
D.
BorisSpasskyTitleBeforeMatch
Indicates the official title or status Boris Spassky held prior to a particular match.
-
E.
RussianChampionshipWinner
Indicates that the subject is the winner of a Russian national championship in a specified field or competition.
- 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_69f76dbde1c08190a24e7f9beb564c8d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f782f416c081908bdd9b1ad456f0e2 |
completed | May 3, 2026, 5:16 p.m. |
Created at: May 3, 2026, 4 p.m.