Triple
T34785238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Chess Championship 2000 |
E1002786
|
entity |
| Predicate | finalScoreWhitePlayer |
P197107
|
FINISHED |
| Object | 8.5 |
—
|
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: 8.5 | Statement: [World Chess Championship 2000, finalScoreWhitePlayer, 8.5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalScoreWhitePlayer Context triple: [World Chess Championship 2000, finalScoreWhitePlayer, 8.5]
-
A.
finalScoreWinner
Indicates that the referenced entity is the winner as determined by the final score of a game, match, or competition.
-
B.
finalScore
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
C.
finalReplayScore
Indicates the score or result achieved at the end of a replayed event, game, or scenario.
-
D.
opponentFinalScore
Indicates the final score achieved by an opposing participant or team in a contest or game.
-
E.
finalSetScore
Indicates the final score achieved in a particular set within a match or game.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
| PDg | Predicate description generation | batch_69fe779167648190936bd49cc1049178 |
completed | May 8, 2026, 11:53 p.m. |
Created at: May 3, 2026, 3:59 p.m.