Triple
T3144462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHL All-Star Game |
E65729
|
entity |
| Predicate | ruleModification |
P24476
|
FINISHED |
| Object | reduced physical play |
—
|
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: reduced physical play | Statement: [NHL All-Star Game, ruleModification, reduced physical play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruleModification Context triple: [NHL All-Star Game, ruleModification, reduced physical play]
-
A.
typicalRuleModification
chosen
Indicates a change made to a standard or default rule, adjusting how that rule normally applies or operates.
-
B.
modification
Indicates a change made to an existing entity, altering its properties, structure, or state from a prior version.
-
C.
leafModification
Indicates a relationship where an entity undergoes or causes a change in the structure, form, or characteristics of a leaf.
-
D.
laterModification
Indicates that one entity is a modification or revision that occurs after another in time.
-
E.
claimsToModify
Indicates that one entity asserts it can change, alter, or adjust another entity or its properties.
- 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_69ad8582f564819088c27e1f96153938 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada595d4548190b720a6131817833b |
completed | March 8, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfa3d9081908425aa636bb9b897 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.