Triple
T109135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2002 IIHF World Championship final |
E2203
|
entity |
| Predicate | overtimePlayed |
P5853
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [2002 IIHF World Championship final, overtimePlayed, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overtimePlayed Context triple: [2002 IIHF World Championship final, overtimePlayed, no]
-
A.
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.
-
B.
overtimeRule
Indicates the rule or policy that defines when and how overtime work is calculated or applied.
-
C.
overtimeFormatRegularSeason
Indicates the format or rules used for overtime periods specifically during the regular season.
-
D.
gamesPlayed
Indicates the number or set of games that an entity has participated in or completed.
-
E.
playoffAppearances
Indicates the number of times an entity (such as a team or player) has qualified for and participated in postseason playoff 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a25711f6788190a22252ea3a3af394 |
completed | Feb. 28, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69a2563fd2fc819090265edbfe3092d6 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2570f45bc81909ebba7ee5f602976 |
completed | Feb. 28, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.