Triple

T8867260
Position Surface form Disambiguated ID Type / Status
Subject Intel 8085 E211049 entity
Predicate hasRST65Interrupt P85081 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: [Intel 8085, hasRST65Interrupt, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRST65Interrupt
Context triple: [Intel 8085, hasRST65Interrupt, true]
  • A. hasInterruptController
    Indicates that an entity is associated with or includes an interrupt controller responsible for managing hardware or software interrupts.
  • B. hasBusArbitration
    Indicates that one entity manages or participates in the control and coordination of access to a shared communication bus among multiple entities.
  • C. hasOutputShortCircuitProtection
    Indicates that an entity provides or is equipped with protection against short circuits occurring at its output.
  • D. hasClockInput
    Indicates that an entity receives a clock signal from another entity as an input for timing or synchronization purposes.
  • E. hasIndication
    Indicates that one entity (typically a product, treatment, or intervention) is intended, approved, or suitable for use in addressing, preventing, or managing a particular condition, purpose, or circumstance.
  • 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_69ca838d3c7c8190a849566d5afd2b11 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc6108530c819084559f4de669ce20 completed April 1, 2026, 12:04 a.m.
PD Predicate disambiguation batch_69cc5c279ea481908c71756f694b66bf completed March 31, 2026, 11:43 p.m.
PDg Predicate description generation batch_69cc5cffe8ec819084c12770fe0578f2 completed March 31, 2026, 11:47 p.m.
Created at: March 30, 2026, 6:51 p.m.