Triple
T37363516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Group A (2021 IIHF World Championship) |
E927643
|
entity |
| Predicate | pointForWinInRegulation |
P24875
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Group A (2021 IIHF World Championship), pointForWinInRegulation, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointForWinInRegulation Context triple: [Group A (2021 IIHF World Championship), pointForWinInRegulation, 3]
-
A.
pointsForOvertimeOrShootoutWin
Indicates that a team is awarded points specifically for winning a game in overtime or a shootout.
-
B.
decidedInRegulationTime
Indicates that the outcome of a contest or match was determined within the standard allotted duration, without requiring any extra time or tiebreak procedures.
-
C.
pointsForShootoutWin
Indicates the number of points awarded to a team for winning a game via a shootout.
-
D.
pointsForWin
chosen
Indicates the number of points awarded to an entity for achieving a win in a given context or competition.
-
E.
pointsScored
Indicates the number of points an entity has earned or achieved in a particular event, game, or context.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:16 p.m.