Triple
T34977556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Chess Championship 2007 |
E1008721
|
entity |
| Predicate | resultScoreOfRunnerUp |
P38172
|
FINISHED |
| Object | 8.0/14 |
—
|
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.0/14 | Statement: [World Chess Championship 2007, resultScoreOfRunnerUp, 8.0/14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultScoreOfRunnerUp Context triple: [World Chess Championship 2007, resultScoreOfRunnerUp, 8.0/14]
-
A.
runnerUpScore
chosen
Indicates the score achieved by the participant or entity that finished in second place in a competition or ranking.
-
B.
secondRunnerUp
Indicates that one entity finished in third place in a competition or ranking relative to the others.
-
C.
secondRoundRunnerUp
Indicates that an entity finished in third place (runner-up to the runner-up) in the second round of a competition or selection process.
-
D.
stateOfRunnerUpTeam
Indicates the state or region associated with the team that finished as the runner-up in a competition or event.
-
E.
runnerUpRank
Indicates the position or ranking assigned to an entity that finishes immediately after the winner (or near the top) in a competition or ordered list.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: May 3, 2026, 4:01 p.m.