Triple
T37363519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Group A (2021 IIHF World Championship) |
E927643
|
entity |
| Predicate | pointForRegulationLoss |
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 (2021 IIHF World Championship), pointForRegulationLoss, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointForRegulationLoss Context triple: [Group A (2021 IIHF World Championship), pointForRegulationLoss, 0]
-
A.
pointsForRegulationLoss
chosen
Indicates the number of points awarded to a team or player specifically for losing a game in regulation time.
-
B.
regionOfLoss
Indicates the anatomical or spatial area where a loss, damage, or deficit occurs or is localized.
-
C.
estimatedPrincipalLoss
Indicates the amount of principal that is expected to be lost on an investment, loan, or financial position.
-
D.
usesPointsForLoss
Indicates that a system or rule assigns or deducts points to represent or account for a loss.
-
E.
pointDefinition
Indicates that one entity serves as the defining description or specification of a particular point in another entity.
- 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_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:16 p.m.