Triple
T25601932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2003–04 NHL season |
E641809
|
entity |
| Predicate | lockoutImpact |
P57235
|
FINISHED |
| Object | followed by full-season cancellation in 2004–05 |
—
|
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: followed by full-season cancellation in 2004–05 | Statement: [2003–04 NHL season, lockoutImpact, followed by full-season cancellation in 2004–05]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lockoutImpact Context triple: [2003–04 NHL season, lockoutImpact, followed by full-season cancellation in 2004–05]
-
A.
supportsLockoutType
Indicates that one entity is compatible with or able to operate using a specified lockout type.
-
B.
hostImpact
Indicates that one entity causes an effect, influence, or change on another entity that acts as its host.
-
C.
effectOfDisabling
Indicates the outcome or consequence that results when something is turned off, deactivated, or made nonfunctional.
-
D.
associatedConflictImpact
chosen
Indicates a relationship where an entity is linked to a specific conflict and the effects or consequences that conflict has on it.
-
E.
effectOnUser
Indicates how an action, event, or condition influences or impacts a user.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9a7d7d881909014fdf3746f981b |
completed | May 2, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 4:31 p.m.