Triple
T8831097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Conference (AHL) |
E210142
|
entity |
| Predicate | pointsForOvertimeOrShootoutLoss |
P84897
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Eastern Conference (AHL), pointsForOvertimeOrShootoutLoss, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointsForOvertimeOrShootoutLoss Context triple: [Eastern Conference (AHL), pointsForOvertimeOrShootoutLoss, 1]
-
A.
pointsForShootoutWin
Indicates the number of points awarded to a team for winning a game via a shootout.
-
B.
pointsScoredByLosingTeam
Indicates the number of points scored by the team that did not win in a given game or match.
-
C.
penaltyGoalPoints
Indicates that points are awarded for a goal scored from a penalty situation.
-
D.
penaltyShootoutScore
Indicates the number of goals each side scored during a penalty shootout used to decide a tied match.
-
E.
pointsScored
Indicates the number of points an entity has earned or achieved in a particular event, game, or context.
- 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_69ca8365b28081909e48e45e95dfc405 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc604ed2b88190b4f53b34b5a438f7 |
completed | April 1, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69cc5c23d08481908d8c9b0ad3d1dc00 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:47 p.m.