Triple
T34803421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OHL regular season |
E1003280
|
entity |
| Predicate | pointsForOvertimeLoss |
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: [OHL regular season, pointsForOvertimeLoss, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointsForOvertimeLoss Context triple: [OHL regular season, pointsForOvertimeLoss, 1]
-
A.
pointsForOvertimeOrShootoutLoss
chosen
Indicates the number of points awarded to a team specifically for losing a game in overtime or a shootout.
-
B.
regularSeasonOvertimeLosses
Indicates the number of games a team lost in overtime during the regular season.
-
C.
pointsForOvertimeOrShootoutWin
Indicates that a team is awarded points specifically for winning a game in overtime or a shootout.
-
D.
pointsScoredByLosingTeam
Indicates the number of points scored by the team that did not win in a given game or match.
-
E.
overtimePlayed
Indicates that an activity, event, or game continued beyond its regular or scheduled duration into an additional overtime period.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77a8bcfa48190ad0f0df94b2301f8 |
completed | May 3, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_69f7795b1abc8190823664d1caa94649 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.