Triple
T33163571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motorola 6802 |
E848814
|
entity |
| Predicate | hasOnChipRAM |
P165026
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Motorola 6802, hasOnChipRAM, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnChipRAM Context triple: [Motorola 6802, hasOnChipRAM, true]
-
A.
hasOnChip
chosen
Indicates that one component or system includes another component integrated directly onto the same chip or integrated circuit.
-
B.
hasRAM
Indicates that an entity possesses or is equipped with a specified amount or type of random-access memory (RAM).
-
C.
typicalRAMRange
Indicates the usual or commonly expected range of RAM capacity associated with an entity.
-
D.
hasOnChipMMUVariantName
Indicates that an entity has a specific named variant of an on-chip Memory Management Unit (MMU) associated with it.
-
E.
maxRAMChipsSupported
Indicates the maximum number of RAM chips that a system or component can support.
- 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_69f3495be8808190bbf427733df08aad |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 1, 2026, 1:28 a.m.