Triple
T34863029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Chess Championship 2004 |
E1004931
|
entity |
| Predicate | gameResultScoring |
P2625
|
FINISHED |
| Object | win = 1 point |
—
|
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: win = 1 point | Statement: [World Chess Championship 2004, gameResultScoring, win = 1 point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameResultScoring Context triple: [World Chess Championship 2004, gameResultScoring, win = 1 point]
-
A.
gameOutcome
Indicates the result or final status of a game, such as which side won, lost, or if it ended in a draw.
-
B.
finalScore
chosen
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
C.
decidingGameWinner
Indicates that an event, action, or process determines which participant is the winner of a game.
-
D.
resultOfMatch
Indicates that one entity is the outcome or product produced by a particular match or matching event involving another entity.
-
E.
game6FinalScore
Indicates the final score achieved in the sixth game of a series or sequence of games.
- 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_69f76dbb678081909a247b9b5e1a73ac |
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. |
Created at: May 3, 2026, 4 p.m.