Triple
T14389185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MOS Technology 6502 |
E356797
|
entity |
| Predicate | usesStackPage |
P114054
|
FINISHED |
| Object | page 1 (addresses $0100–$01FF) |
—
|
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: page 1 (addresses $0100–$01FF) | Statement: [MOS Technology 6502, usesStackPage, page 1 (addresses $0100–$01FF)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStackPage Context triple: [MOS Technology 6502, usesStackPage, page 1 (addresses $0100–$01FF)]
-
A.
supportsStateStack
Indicates that one entity provides or maintains a stack-based mechanism for storing, managing, and restoring multiple states over time.
-
B.
hasStacks
Indicates that one entity possesses or contains multiple layered or piled units of another entity.
-
C.
isStackedWith
Indicates that one object is positioned directly on top of or beneath another object so that they form a vertical stack together.
-
D.
callStackMechanism
Indicates a relationship where one process or component manages, tracks, or manipulates the sequence of active function or method calls in a call stack.
-
E.
hasStackPointer
Indicates that an entity maintains or uses a specific stack pointer reference within a stack-based memory or execution context.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9029ef048190bdda5ee41618e720 |
completed | April 14, 2026, 7:06 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
| PDg | Predicate description generation | batch_69de2e08b6c08190bb4c929deab236a6 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:16 a.m.