Triple
T20165957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharp LR35902 |
E491824
|
entity |
| Predicate | supportsInterrupt |
P138931
|
FINISHED |
| Object | V-Blank interrupt |
—
|
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: V-Blank interrupt | Statement: [Sharp LR35902, supportsInterrupt, V-Blank interrupt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsInterrupt Context triple: [Sharp LR35902, supportsInterrupt, V-Blank interrupt]
-
A.
supportsInterruptMasking
Indicates that one entity provides the capability to temporarily disable or mask interrupts for another entity or operation.
-
B.
wasInterruptedBy
Indicates that an ongoing event, action, or process was stopped or disrupted by another event, action, or agent.
-
C.
supportsSuspension
Indicates that one entity provides the necessary structure, strength, or mechanism to hold or keep another entity suspended.
-
D.
possibleInterruption
Indicates that one event, action, or process may interrupt, break into, or otherwise disrupt the continuity of another.
-
E.
hasInterruptController
Indicates that an entity is associated with or includes an interrupt controller responsible for managing hardware or software interrupts.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e668442d2c81908bb1a0fac9895b5e |
completed | April 20, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:35 p.m.