Triple
T34785150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin Defense |
E1002784
|
entity |
| Predicate | usedInFamousMatch |
P197812
|
FINISHED |
| Object | Kramnik vs Kasparov World Championship 2000 |
—
|
NE NERFINISHED |
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: Kramnik vs Kasparov World Championship 2000 | Statement: [Berlin Defense, usedInFamousMatch, Kramnik vs Kasparov World Championship 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInFamousMatch Context triple: [Berlin Defense, usedInFamousMatch, Kramnik vs Kasparov World Championship 2000]
-
A.
famousMatch
Indicates that two entities are linked by a match or pairing that is widely known or celebrated.
-
B.
usedInOfficialMatchReports
Indicates that something is included or referenced within formal, authoritative match reports.
-
C.
playedInMatch
Indicates that an entity participated as a player in a particular match.
-
D.
notableTournamentPerformance
Indicates that an entity achieved a significant or distinguished result or showing in a competitive tournament.
-
E.
hasIconicShot
Indicates that a work, scene, or moment contains a visually memorable or culturally recognizable shot that is widely regarded as iconic.
- 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_69feabcda59481908f2bc13b46fcced1 |
completed | May 9, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69feaabd63f88190b30dcf6dd2ea39d1 |
completed | May 9, 2026, 3:32 a.m. |
| PDg | Predicate description generation | batch_69feabcca6148190a8eb7b6fa33729c7 |
completed | May 9, 2026, 3:36 a.m. |
Created at: May 3, 2026, 3:59 p.m.