Triple
T12576901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motorola 68010 |
E300230
|
entity |
| Predicate | registerSet |
P105519
|
FINISHED |
| Object | 16 32-bit registers |
—
|
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: 16 32-bit registers | Statement: [Motorola 68010, registerSet, 16 32-bit registers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registerSet Context triple: [Motorola 68010, registerSet, 16 32-bit registers]
-
A.
setsIn
Indicates that one entity places or positions another entity into or within a specified container, location, or context.
-
B.
set
Indicates that an entity places, positions, or establishes another entity into a particular state, configuration, or location.
-
C.
sets
Indicates that an entity places, positions, or puts another entity into a particular state, location, or configuration.
-
D.
registerPair
Indicates that two entities are formally recorded or linked together as a pair within a system or registry.
-
E.
setsOut
Indicates that an entity begins a journey, course of action, or process, moving from an initial state or location toward a goal or destination.
- 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_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. |
| PDg | Predicate description generation | batch_69d9550af6d48190a40e349ed0424be3 |
completed | April 10, 2026, 7:52 p.m. |
Created at: April 9, 2026, 4:51 p.m.