Triple
T33163572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motorola 6802 |
E848814
|
entity |
| Predicate | hasOnChipOscillator |
P182279
|
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, hasOnChipOscillator, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnChipOscillator Context triple: [Motorola 6802, hasOnChipOscillator, true]
-
A.
hasOnChip
Indicates that one component or system includes another component integrated directly onto the same chip or integrated circuit.
-
B.
hasChipType
Indicates that an entity is associated with or uses a specific type or category of chip.
-
C.
hasMicrocontroller
Indicates that an entity contains, includes, or is equipped with a microcontroller as one of its components.
-
D.
hasInternalFrequencyCompensation
Indicates that an electronic component or circuit includes built-in circuitry to stabilize its frequency response without requiring external compensation components.
-
E.
hasMicrocontrollerCore
Indicates that one entity incorporates or contains a microcontroller core as part of its internal components or architecture.
- 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_69f3495be8808190bbf427733df08aad |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7886b27f08190ab4580f949222c93 |
completed | May 3, 2026, 5:39 p.m. |
Created at: May 1, 2026, 1:28 a.m.