Triple
T26333616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zilog Z8000 |
E662458
|
entity |
| Predicate | supportsInterruptPriorities |
P196649
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Zilog Z8000, supportsInterruptPriorities, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsInterruptPriorities Context triple: [Zilog Z8000, supportsInterruptPriorities, true]
-
A.
supportsInterrupt
Indicates that one entity is capable of handling or accommodating an interruption initiated by another entity.
-
B.
supportsInterruptMasking
Indicates that one entity provides the capability to temporarily disable or mask interrupts for another entity or operation.
-
C.
hasInterruptModes
Indicates that an entity supports or is associated with one or more specific modes in which it can be interrupted or can handle interrupts.
-
D.
supportsRasterInterrupts
Indicates that the system or component is capable of handling raster interrupts during display or rendering operations.
-
E.
supportsAutovectorInterrupts
Indicates that an entity provides or is compatible with automatic vector-based interrupt handling mechanisms.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
| PDg | Predicate description generation | batch_69fe610d75a48190bfd08a9bb957fcd3 |
completed | May 8, 2026, 10:17 p.m. |
Created at: April 26, 2026, 10:35 p.m.