Triple
T11293195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2007–08 NHL season |
E267380
|
entity |
| Predicate | lockoutShortened |
P80659
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [2007–08 NHL season, lockoutShortened, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lockoutShortened Context triple: [2007–08 NHL season, lockoutShortened, no]
-
A.
lockedMeans
Indicates that one state, condition, or action guarantees or necessitates another, such that when the first is "locked in," the second must follow.
-
B.
wasShortened
chosen
Indicates that something has been made shorter in length, duration, or extent compared to its original form.
-
C.
lockType
Indicates the specific kind or category of locking mechanism or access restriction applied to an entity or resource.
-
D.
isShort
Indicates that one entity has a relatively small height, length, or duration compared to a standard or to other entities.
-
E.
locks
Indicates that one entity secures, fastens, or restricts access to another entity, typically preventing its use or opening without proper authorization or a key.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e98b149481909f432a6b9ef8bfbb |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a6ca2c8190afdc24b61ccd3f8a |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.