Triple
T7304476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zilog Z80 |
E167939
|
entity |
| Predicate | supportsInterruptMode |
P29735
|
FINISHED |
| Object | IM 0 |
—
|
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: IM 0 | Statement: [Zilog Z80, supportsInterruptMode, IM 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsInterruptMode Context triple: [Zilog Z80, supportsInterruptMode, IM 0]
-
A.
supportsGuardIntervals
Indicates that one entity provides or is compatible with guard intervals used by another entity in a timing- or transmission-related context.
-
B.
isStateSupported
chosen
Indicates that a particular state or condition is recognized, allowed, or handled within a given system or context.
-
C.
supportsSuspension
Indicates that one entity provides the necessary structure, strength, or mechanism to hold or keep another entity suspended.
-
D.
supportsUserInteraction
Indicates that an entity enables or facilitates direct interaction with a user, such as receiving input or providing responsive feedback.
-
E.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
- 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebb352ec8190846eff044e08805e |
completed | March 27, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:01 p.m.