Triple
T36165650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WDC 65C816 |
E1045989
|
entity |
| Predicate | supportsStackRelativeAddressing |
P204772
|
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, supportsStackRelativeAddressing, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsStackRelativeAddressing Context triple: [WDC 65C816, supportsStackRelativeAddressing, true]
-
A.
hasStackPointer
Indicates that an entity maintains or uses a specific stack pointer reference within a stack-based memory or execution context.
-
B.
supportsMultipleStacks
Indicates that the subject is capable of handling or maintaining more than one stack simultaneously.
-
C.
hasAlternativeStack
Indicates that an entity is associated with a different or substitute stack configuration or implementation that can be used in place of the primary one.
-
D.
supportsByteAddressing
Indicates that one entity provides the capability for direct access to individual bytes within its addressable memory or data space for another entity.
-
E.
stackLocation
Indicates the position or placement of an item within a stack or layered arrangement.
- 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.