Triple
T36165661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WDC 65C816 |
E1045989
|
entity |
| Predicate | emulationModeVectorBank |
P185381
|
FINISHED |
| Object | bank 0 |
—
|
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: bank 0 | Statement: [WDC 65C816, emulationModeVectorBank, bank 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emulationModeVectorBank Context triple: [WDC 65C816, emulationModeVectorBank, bank 0]
-
A.
emulationModeIndexRegisterSize
Indicates the size of the index register used when the system or processor is operating in emulation mode.
-
B.
emulationModeAccumulatorSize
Indicates the size of the accumulator used when operating in emulation mode.
-
C.
emulates
Indicates that one entity imitates or reproduces the behavior, function, or characteristics of another.
-
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.
supportsVirtual8086Mode
Indicates that a processor or system is capable of operating in and managing virtual 8086 (v86) mode for running real-mode tasks in a protected environment.
- 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_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be520f148190ba200bf3dbf40656 |
completed | May 3, 2026, 9:29 p.m. |
Created at: May 3, 2026, 4:08 p.m.