Triple
T8867254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel 8085 |
E211049
|
entity |
| Predicate | hasOnChipClockGenerator |
P5737
|
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: [Intel 8085, hasOnChipClockGenerator, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnChipClockGenerator Context triple: [Intel 8085, hasOnChipClockGenerator, true]
-
A.
hasClockInput
Indicates that an entity receives a clock signal from another entity as an input for timing or synchronization purposes.
-
B.
hasClockSpeed
Indicates that an entity (typically a processor or device) operates at a specified clock frequency or speed.
-
C.
hasInternalFrequencyCompensation
Indicates that an electronic component or circuit includes built-in circuitry to stabilize its frequency response without requiring external compensation components.
-
D.
hasClock
chosen
Indicates that one entity possesses, contains, or is equipped with a clock.
-
E.
hasMicrocontrollerCore
Indicates that one entity incorporates or contains a microcontroller core as part of its internal components or architecture.
- 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_69ca838d3c7c8190a849566d5afd2b11 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6108530c819084559f4de669ce20 |
completed | April 1, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69cc5c279ea481908c71756f694b66bf |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:51 p.m.