Triple
T15264770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHL Centennial Classic |
E364869
|
entity |
| Predicate | regulationScoreAfterThreePeriods |
P117874
|
FINISHED |
| Object | 4–4 |
—
|
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: 4–4 | Statement: [NHL Centennial Classic, regulationScoreAfterThreePeriods, 4–4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulationScoreAfterThreePeriods Context triple: [NHL Centennial Classic, regulationScoreAfterThreePeriods, 4–4]
-
A.
regulationScore
Indicates the degree or quality of how well something is controlled, managed, or kept within desired limits.
-
B.
regulationMinutes
Indicates the number of minutes played during the standard regulation period of a game, excluding any overtime or extra periods.
-
C.
succeedsRegulationCycle
Indicates that one regulation cycle occurs after and directly follows another in a sequence.
-
D.
pointsAfterThreeQuarters
Indicates the number of points an entity has accumulated by the end of the third quarter of a game or event.
-
E.
regulationEra
Indicates the historical or temporal period during which a particular regulation or regulatory framework was in effect.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00851c5b88190a296b6a105d3ee30 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:14 a.m.