Triple
T26176735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IX |
E654562
|
entity |
| Predicate | usedByInstructionSet |
P168560
|
FINISHED |
| Object | Z80 instruction set |
—
|
NE NERFINISHED |
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: Z80 instruction set | Statement: [IX, usedByInstructionSet, Z80 instruction set]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByInstructionSet Context triple: [IX, usedByInstructionSet, Z80 instruction set]
-
A.
usedByInstruction
chosen
Indicates that something (such as a resource, value, or object) is utilized or referenced by a particular instruction.
-
B.
hasInstructionSet
Indicates that one entity (typically a processor or system) is defined as using or supporting a particular instruction set.
-
C.
instructionSetType
Indicates the type or category of an instruction set associated with a processor or computing architecture.
-
D.
instructionSetSize
Indicates the size or number of instructions defined in an instruction set.
-
E.
instructionSetExtensions
Indicates that one entity defines, supports, or includes additional instruction set features or extensions relative to another.
- 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 26, 2026, 8:38 p.m.