Triple
T36165651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WDC 65C816 |
E1045989
|
entity |
| Predicate | stackPointerWidth |
P184985
|
FINISHED |
| Object | 16-bit in native mode |
—
|
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: 16-bit in native mode | Statement: [WDC 65C816, stackPointerWidth, 16-bit in native mode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stackPointerWidth Context triple: [WDC 65C816, stackPointerWidth, 16-bit in native mode]
-
A.
hasStackPointer
Indicates that an entity maintains or uses a specific stack pointer reference within a stack-based memory or execution context.
-
B.
stackGrowthDirection
Indicates the direction in which a stack grows in memory (e.g., toward higher or lower addresses) during push operations.
-
C.
stackLocation
Indicates the position or placement of an item within a stack or layered arrangement.
-
D.
stackStructure
Indicates that one entity is arranged on top of or in a layered order relative to another, forming a stack-like structure.
-
E.
armSpan
Indicates the distance between an individual's outstretched fingertips, typically measured from one hand to the other across the body.
- 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_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b69a74a08190b31b1201278a2c57 |
completed | May 3, 2026, 8:56 p.m. |
Created at: May 3, 2026, 4:08 p.m.