Triple
T33163593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motorola 6802 |
E848814
|
entity |
| Predicate | supportsMaskableInterrupt |
P85088
|
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: [Motorola 6802, supportsMaskableInterrupt, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMaskableInterrupt Context triple: [Motorola 6802, supportsMaskableInterrupt, true]
-
A.
supportsInterruptMasking
chosen
Indicates that one entity provides the capability to temporarily disable or mask interrupts for another entity or operation.
-
B.
supportsInterrupt
Indicates that one entity is capable of handling or accommodating an interruption initiated by another entity.
-
C.
supportsInterruptPriorities
Indicates that one entity provides or is compatible with a mechanism for assigning and handling different priority levels for interrupts associated with another entity.
-
D.
supportsAutovectorInterrupts
Indicates that an entity provides or is compatible with automatic vector-based interrupt handling mechanisms.
-
E.
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.
- 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_69f3495be8808190bbf427733df08aad |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:28 a.m.