Triple
T36165658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WDC 65C816 |
E1045989
|
entity |
| Predicate | supports16BitImmediateOperands |
P204773
|
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, supports16BitImmediateOperands, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supports16BitImmediateOperands Context triple: [WDC 65C816, supports16BitImmediateOperands, true]
-
A.
supports32BitRegistersViaPairing
Indicates that the system can handle 32-bit registers by pairing smaller-width registers together to emulate 32-bit behavior.
-
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.
supportsIndexRegisters
Indicates that an entity (such as a processor or instruction set) is capable of using index registers to modify or calculate memory addresses during operations.
-
D.
supportsIntegerOperations
Indicates that the subject is capable of performing or handling operations involving integer values.
-
E.
supportsByteAddressing
Indicates that one entity provides the capability for direct access to individual bytes within its addressable memory or data space for another entity.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:08 p.m.