Triple
T12576903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motorola 68010 |
E300230
|
entity |
| Predicate | addressRegisters |
P23434
|
FINISHED |
| Object | 8 address registers (A0–A7) |
—
|
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: 8 address registers (A0–A7) | Statement: [Motorola 68010, addressRegisters, 8 address registers (A0–A7)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressRegisters Context triple: [Motorola 68010, addressRegisters, 8 address registers (A0–A7)]
-
A.
addresses
Indicates that one entity directs speech, communication, or written correspondence specifically toward another entity.
-
B.
addressAllocation
Indicates the assignment or reservation of an address (such as an IP or memory address) for use by a specific entity or resource.
-
C.
addressingMechanism
Indicates the method or system used to identify, locate, or reference a target within a larger space, network, or structure.
-
D.
addressMode
chosen
Indicates how data or resources are accessed or referenced within a system, such as the method or scheme used to locate them.
-
E.
address
Indicates that one entity directs spoken or written communication specifically to another entity.
- 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9550d84908190aea0f50055f6d92e |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95414692881909c52a1de7d224b44 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 4:51 p.m.