Triple
T8952448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motorola 6800 |
E213385
|
entity |
| Predicate | resetVectorAddress |
P85846
|
FINISHED |
| Object | 0xFFFE |
—
|
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: 0xFFFE | Statement: [Motorola 6800, resetVectorAddress, 0xFFFE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resetVectorAddress Context triple: [Motorola 6800, resetVectorAddress, 0xFFFE]
-
A.
resetType
Indicates the specific kind or method of reset applied to an entity, process, or system state.
-
B.
addressingMechanism
Indicates the method or system used to identify, locate, or reference a target within a larger space, network, or structure.
-
C.
sectionAddressed
Indicates that a specific section or part of a document, text, or resource is being referred to, targeted, or dealt with by an action or statement.
-
D.
addressedBranch
Indicates that an action, communication, or item is specifically directed to or associated with a particular branch of an organization or network.
-
E.
addressMode
Indicates how data or resources are accessed or referenced within a system, such as the method or scheme used to locate them.
- 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_69ca8399ad2081909f8fa41d4314c215 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc670dc0c88190b1f59e96ad88e4ee |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f887108819096d45a186fc137b3 |
completed | March 31, 2026, 11:58 p.m. |
Created at: March 30, 2026, 6:59 p.m.