Triple

T12576907
Position Surface form Disambiguated ID Type / Status
Subject Motorola 68010 E300230 entity
Predicate supportsAutovectorInterrupts P105522 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 68010, supportsAutovectorInterrupts, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsAutovectorInterrupts
Context triple: [Motorola 68010, supportsAutovectorInterrupts, true]
  • A. supportsInterruptMasking
    Indicates that one entity provides the capability to temporarily disable or mask interrupts for another entity or operation.
  • B. supportsAVX
    Indicates that one entity provides or is compatible with AVX (Advanced Vector Extensions) functionality for another entity or operation.
  • C. supportsAVX2
    Indicates that one entity provides or has compatibility with AVX2 (Advanced Vector Extensions 2) instruction set capabilities for another.
  • D. hasInterruptController
    Indicates that an entity is associated with or includes an interrupt controller responsible for managing hardware or software interrupts.
  • E. supportsIntelVT-x
    Indicates that one entity provides compatibility with or the capability to use Intel VT-x virtualization technology for another entity.
  • 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_69d7bde87b648190bcd0266e9efde098 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d9550d84908190aea0f50055f6d92e completed April 10, 2026, 7:52 p.m.
PD Predicate disambiguation batch_69d95414692881909c52a1de7d224b44 completed April 10, 2026, 7:48 p.m.
PDg Predicate description generation batch_69d9550af6d48190a40e349ed0424be3 completed April 10, 2026, 7:52 p.m.
Created at: April 9, 2026, 4:51 p.m.