Triple
T28996503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Chess Championship |
E736179
|
entity |
| Predicate | tieBreakFormat |
P146212
|
FINISHED |
| Object | rapid games |
—
|
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: rapid games | Statement: [World Chess Championship, tieBreakFormat, rapid games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tieBreakFormat Context triple: [World Chess Championship, tieBreakFormat, rapid games]
-
A.
tieBreakerMetric
chosen
Indicates a metric used to resolve ties when primary comparison criteria result in equal values.
-
B.
tieBreakerAppointedBy
Indicates that a specific party or authority is responsible for appointing the individual or entity who will act as the tie-breaker in a decision-making process.
-
C.
tiebreaker
Indicates that one entity serves as the deciding factor used to break a tie between two or more otherwise equal options or outcomes.
-
D.
useTiebreakers
Indicates that when primary criteria result in a tie, additional predefined rules or factors are applied to determine a winner or ordering.
-
E.
tiebreakerGameLoser
Indicates the player or team that lost a specific tiebreaker game used to resolve a tie in a competition or match.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fb6ef4881909a758c3538fdec03 |
completed | May 2, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:31 a.m.