Triple
T27072095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Blitz Chess Championship 2013 |
E685354
|
entity |
| Predicate | tieBreakSystem |
P146212
|
FINISHED |
| Object | Buchholz |
—
|
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: Buchholz | Statement: [World Blitz Chess Championship 2013, tieBreakSystem, Buchholz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tieBreakSystem Context triple: [World Blitz Chess Championship 2013, tieBreakSystem, Buchholz]
-
A.
tiebreaker
Indicates that one entity serves as the deciding factor used to break a tie between two or more otherwise equal options or outcomes.
-
B.
tieBreakerMetric
chosen
Indicates a metric used to resolve ties when primary comparison criteria result in equal values.
-
C.
useTiebreakers
Indicates that when primary criteria result in a tie, additional predefined rules or factors are applied to determine a winner or ordering.
-
D.
tiebreakerGameLoser
Indicates the player or team that lost a specific tiebreaker game used to resolve a tie in a competition or match.
-
E.
usesHeadToHeadAsTiebreaker
Indicates that a head-to-head comparison between entities is used to break a tie in their ranking or outcome.
- 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6231257f481909d576c19559e0ad0 |
completed | May 2, 2026, 4:15 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:28 a.m.