Triple
T29372199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YM-2151 |
E744882
|
entity |
| Predicate | hasInterruptOutput |
P165951
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [YM-2151, hasInterruptOutput, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInterruptOutput Context triple: [YM-2151, hasInterruptOutput, yes]
-
A.
hasInterruptController
Indicates that an entity is associated with or includes an interrupt controller responsible for managing hardware or software interrupts.
-
B.
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.
-
C.
hasIRQOutput
chosen
Indicates that an entity provides or exposes an interrupt request (IRQ) output signal to another component or system.
-
D.
hasOutputStatus
Indicates that an entity is associated with a particular state or condition of its produced output.
-
E.
hasOutputShortCircuitProtection
Indicates that an entity provides or is equipped with protection against short circuits occurring at its output.
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fe86cad5108190b0164b8bc6fc23ea |
completed | May 9, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69fe83c0c9888190b6fc40c7f727b569 |
completed | May 9, 2026, 12:45 a.m. |
Created at: April 28, 2026, 2:28 p.m.