Triple
T19097527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Group A (2019 IIHF World Championship) |
E467445
|
entity |
| Predicate | pointsForRegulationLoss |
P134356
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [Group A (2019 IIHF World Championship), pointsForRegulationLoss, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointsForRegulationLoss Context triple: [Group A (2019 IIHF World Championship), pointsForRegulationLoss, 0]
-
A.
usesPointsForLoss
Indicates that a system or rule assigns or deducts points to represent or account for a loss.
-
B.
penaltyPoints
Indicates that a certain number of negative points or demerits are assigned to an entity as a consequence of a rule violation, error, or infraction.
-
C.
regulationScore
Indicates the degree or quality of how well something is controlled, managed, or kept within desired limits.
-
D.
pointsForWin
Indicates the number of points awarded to an entity for achieving a win in a given context or competition.
-
E.
pointsForOvertimeOrShootoutLoss
Indicates the number of points awarded to a team specifically for losing a game in overtime or a shootout.
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e36b279c819091a8d51f044bc644 |
completed | April 20, 2026, 8:27 a.m. |
| PD | Predicate disambiguation | batch_69e4b9ac41848190afd0f33b42cebe99 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.