Triple
T27791475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2003 Calder Cup playoffs |
E701091
|
entity |
| Predicate | qualifyingRoundFormat |
P167790
|
FINISHED |
| Object | best-of-three series |
—
|
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: best-of-three series | Statement: [2003 Calder Cup playoffs, qualifyingRoundFormat, best-of-three series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualifyingRoundFormat Context triple: [2003 Calder Cup playoffs, qualifyingRoundFormat, best-of-three series]
-
A.
firstRoundFormat
Indicates the specific structure or rules used to organize and play the initial round of a multi-round event or competition.
-
B.
secondRoundFormat
Indicates the structure or rules used to organize and conduct the second round of a multi-round process or competition.
-
C.
qualifyingRoundsEndDate
Indicates the date on which the qualifying rounds of an event or process conclude.
-
D.
qualifyingRoundsStartDate
Indicates the date on which the qualifying rounds for an event or competition begin.
-
E.
worldCupFormat
Indicates the specific structure, rules, and progression system used to organize and play a given World Cup competition.
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f66cf092c881908d7034c9c2bc61d5 |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 27, 2026, 5:28 p.m.