Triple
T32181079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boris Gelfand |
E821982
|
entity |
| Predicate | resultOfWorldChampionshipMatch |
P72340
|
FINISHED |
| Object | lost in rapid tiebreaks |
—
|
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: lost in rapid tiebreaks | Statement: [Boris Gelfand, resultOfWorldChampionshipMatch, lost in rapid tiebreaks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfWorldChampionshipMatch Context triple: [Boris Gelfand, resultOfWorldChampionshipMatch, lost in rapid tiebreaks]
-
A.
resultOfMatch
Indicates that one entity is the outcome or product produced by a particular match or matching event involving another entity.
-
B.
championshipOutcome
chosen
Indicates the result or final standing of a competitor or team in a championship event.
-
C.
subsequentChampionshipResult
Indicates the outcome or result of a championship that occurs immediately after a referenced earlier championship.
-
D.
finalMatches
Indicates that two or more items correspond exactly in their final or completed form, satisfying all criteria for being considered the same at the end state.
-
E.
worldCupMatch
Indicates that a particular game is a match played as part of the FIFA World Cup tournament.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 1, 2026, 12:34 a.m.