Triple
T36165654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WDC 65C816 |
E1045989
|
entity |
| Predicate | supportsMVNInstruction |
P196773
|
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: [WDC 65C816, supportsMVNInstruction, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMVNInstruction Context triple: [WDC 65C816, supportsMVNInstruction, true]
-
A.
supportsBlockMoveInstructions
chosen
Indicates that an entity is capable of handling or executing instructions related to moving blocks.
-
B.
supportsRIMInstruction
Indicates that one entity is capable of handling, executing, or otherwise accommodating a specified RIM (Read-In-Memory or related) instruction associated with another entity.
-
C.
supportsInstruction
Indicates that one entity provides assistance, resources, or functionality that enables or facilitates the instruction or teaching activities of another entity.
-
D.
hasInstructionSet
Indicates that one entity (typically a processor or system) is defined as using or supporting a particular instruction set.
-
E.
supportsInferenceOf
Indicates that one entity provides a logical basis or justification for concluding or deriving 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.