Triple
T36165630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WDC 65C816 |
E1045989
|
entity |
| Predicate | nativeModeAccumulatorSize |
P21839
|
FINISHED |
| Object | 16-bit |
—
|
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 | Statement: [WDC 65C816, nativeModeAccumulatorSize, 16-bit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeModeAccumulatorSize Context triple: [WDC 65C816, nativeModeAccumulatorSize, 16-bit]
-
A.
numberOfAccumulators
Indicates the total count of accumulators associated with or used by a given entity or system.
-
B.
stateSizeBytes
chosen
Indicates the size of a given state or stateful data in terms of the number of bytes it occupies.
-
C.
nestSize
Indicates the typical number of offspring or eggs contained in a single nest for the related entity.
-
D.
hasAccumulator
Indicates that an entity possesses or is equipped with an accumulator component (such as an energy or charge storage unit).
-
E.
stateSize
Indicates the relative or absolute physical extent or dimensions of a state, such as its area or population size.
- 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_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.