Triple
T32025192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Candidates Tournament |
E817797
|
entity |
| Predicate | tieBreakMethods |
P141055
|
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: [Candidates Tournament, tieBreakMethods, rapid games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tieBreakMethods Context triple: [Candidates Tournament, tieBreakMethods, rapid games]
-
A.
tieBreakerMetric
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
chosen
Indicates that when primary criteria result in a tie, additional predefined rules or factors are applied to determine a winner or ordering.
-
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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b46a02988190b2cdfc9a936683b4 |
completed | May 3, 2026, 2:35 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:17 a.m.