Triple
T1317732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHL trade deadline |
E28143
|
entity |
| Predicate | triggers |
P693
|
FINISHED |
| Object | increased trade activity among NHL teams |
—
|
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: increased trade activity among NHL teams | Statement: [NHL trade deadline, triggers, increased trade activity among NHL teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triggers Context triple: [NHL trade deadline, triggers, increased trade activity among NHL teams]
-
A.
triggered
chosen
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
B.
triggerEvent
Indicates that one entity causes or initiates the occurrence of a specific event involving another entity or the system.
-
C.
actsOn
Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
-
D.
trades
Indicates an exchange relationship where one party gives something of value to another in return for something else of value.
-
E.
aftershocks
Indicates that one seismic event occurs as a subsequent, typically smaller tremor following a main earthquake.
- 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_69a498532c3481909223b74af2e578df |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c176c89881909e9dc0e34f12f056 |
completed | March 1, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69a4beebcb348190964bd7215811942c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.