Triple
T24730533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metal Ligaen |
E618270
|
entity |
| Predicate | awardsPointsForOvertimeLoss |
P84897
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Metal Ligaen, awardsPointsForOvertimeLoss, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awardsPointsForOvertimeLoss Context triple: [Metal Ligaen, awardsPointsForOvertimeLoss, yes]
-
A.
pointsForOvertimeOrShootoutLoss
chosen
Indicates the number of points awarded to a team specifically for losing a game in overtime or a shootout.
-
B.
pointsForOvertimeOrShootoutWin
Indicates that a team is awarded points specifically for winning a game in overtime or a shootout.
-
C.
regularSeasonOvertimeLosses
Indicates the number of games a team lost in overtime during the regular season.
-
D.
hasOvertimeWinningMargin
Indicates that one competitor’s margin of victory over another was achieved specifically during an overtime period.
-
E.
penaltyGoalPoints
Indicates that points are awarded for a goal scored from a penalty situation.
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 4:02 a.m.