Triple
T22365854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Conference playoffs |
E552901
|
entity |
| Predicate | hasTiebreakerCriteria |
P146212
|
FINISHED |
| Object | head-to-head record |
—
|
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: head-to-head record | Statement: [Eastern Conference playoffs, hasTiebreakerCriteria, head-to-head record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTiebreakerCriteria Context triple: [Eastern Conference playoffs, hasTiebreakerCriteria, head-to-head record]
-
A.
useTiebreakers
Indicates that when primary criteria result in a tie, additional predefined rules or factors are applied to determine a winner or ordering.
-
B.
usesHeadToHeadAsTiebreaker
Indicates that a head-to-head comparison between entities is used to break a tie in their ranking or outcome.
-
C.
hasTiePossibility
Indicates that a situation, event, or interaction has the potential to end in a tie or draw rather than producing a single winner.
-
D.
tieBreakerMetric
chosen
Indicates a metric used to resolve ties when primary comparison criteria result in equal values.
-
E.
hasComparisonCriterion
Indicates that one entity is used as the basis or standard by which another entity is compared or evaluated.
- 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_69e11e4affcc8190ba7c27d29062558d |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1580074dc819091305ac7017000d3 |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:44 p.m.