Triple
T36165659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WDC 65C816 |
E1045989
|
entity |
| Predicate | resetVectorLocation |
P85846
|
FINISHED |
| Object | bank 0, addresses FFFC–FFFD |
—
|
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, addresses FFFC–FFFD | Statement: [WDC 65C816, resetVectorLocation, bank 0, addresses FFFC–FFFD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resetVectorLocation Context triple: [WDC 65C816, resetVectorLocation, bank 0, addresses FFFC–FFFD]
-
A.
resetVectorAddress
chosen
Indicates resetting the address or location reference of a vector back to a defined initial or default state.
-
B.
targetLocation
Indicates the specific place or destination toward which an action, movement, or effect is directed.
-
C.
deltaLocation
Indicates a change or difference between two locations, typically specifying how one location has shifted relative to another.
-
D.
initialPosition
Indicates the original or starting location of an entity before any movement or change in position occurs.
-
E.
positionOnReconstruction
Indicates that one entity expresses a stance, opinion, or role regarding the process or policy of reconstruction.
- 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_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:08 p.m.