Triple
T8087477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2000 IIHF Women's World Championship |
E188768
|
entity |
| Predicate | overtimeInFinal |
P35409
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [2000 IIHF Women's World Championship, overtimeInFinal, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overtimeInFinal Context triple: [2000 IIHF Women's World Championship, overtimeInFinal, yes]
-
A.
overtimePlayed
Indicates that an activity, event, or game continued beyond its regular or scheduled duration into an additional overtime period.
-
B.
finalAfterExtraTime
chosen
Indicates that the final outcome or result is determined after an additional period of extra time beyond the regular duration.
-
C.
overtimePeriodDuration
Indicates the length of time that an overtime period lasts.
-
D.
usesOvertime
Indicates that one entity makes use of another entity repeatedly or continuously over an extended period of time.
-
E.
overtimeFormatPlayoffs
Indicates that the relationship or action pertains to the specific overtime rules or structure used during playoff games, as distinct from regular-season overtime formats.
- 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_69ca82b662e88190b9323daab8c28a21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4162244481908ab1202a9974deaa |
completed | March 31, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:29 p.m.