Triple
T29184537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boris Spassky |
E739830
|
entity |
| Predicate | worldChampionInChess |
P21542
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Boris Spassky, worldChampionInChess, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldChampionInChess Context triple: [Boris Spassky, worldChampionInChess, yes]
-
A.
RussianChampionshipWinner
Indicates that the subject is the winner of a Russian national championship in a specified field or competition.
-
B.
featuredWorldChampion
Indicates that an entity has been highlighted or showcased specifically in its capacity as a world champion.
-
C.
worldChampionIn
chosen
Indicates that an entity holds or has held the title of world champion in a specified field, discipline, or competition.
-
D.
FIDEWorldChampionshipCycle
Indicates a competitive qualification process or series of events that determine who earns the right to challenge for the FIDE World Chess Championship title.
-
E.
chessRole
Indicates that one entity has a specific role or function in the context of a chess game relative to another entity.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 28, 2026, 11:59 a.m.