Triple
T299991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motorola 68000 family |
E6176
|
entity |
| Predicate | registerWidth |
P4121
|
FINISHED |
| Object | 32-bit general-purpose 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: 32-bit general-purpose registers | Statement: [Motorola 68000 family, registerWidth, 32-bit general-purpose registers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registerWidth Context triple: [Motorola 68000 family, registerWidth, 32-bit general-purpose registers]
-
A.
width
Indicates the measurement of how wide an entity is, typically the extent of its horizontal dimension from side to side.
-
B.
hasWidth
Indicates that an entity possesses a specific measurement or extent along its width dimension.
-
C.
register
Indicates that an entity formally records or enrolls another entity or itself in an official system, list, or record.
-
D.
sizeIncreasedTo
Indicates that an entity’s size has changed and reached a specified larger value or magnitude.
-
E.
bitWidth
chosen
Indicates the number of bits used to represent or encode a given value, type, or data element.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea2fba548190a5aeb1597dca96bd |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e93aff048190a633c8ae2b76a41f |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.