Triple
T34785240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Chess Championship 2000 |
E1002786
|
entity |
| Predicate | gamesPlanned |
P11255
|
FINISHED |
| Object | 16 |
—
|
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: 16 | Statement: [World Chess Championship 2000, gamesPlanned, 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gamesPlanned Context triple: [World Chess Championship 2000, gamesPlanned, 16]
-
A.
postGamesPlan
Indicates that an entity publishes or shares a plan or strategy related to games after they have concluded.
-
B.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
-
C.
plannedDevelopment
Indicates that one entity has been designated or scheduled for future development or construction by another entity.
-
D.
platformPlanned
Indicates that a platform is intended or scheduled to be created, implemented, or made available in the future.
-
E.
planned
chosen
Indicates that an entity has intentionally arranged or scheduled another entity or event to occur in the future.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.