Triple
T9244343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motorola 68030 |
E222148
|
entity |
| Predicate | hasOnChipCache |
P87754
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Motorola 68030, hasOnChipCache, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnChipCache Context triple: [Motorola 68030, hasOnChipCache, yes]
-
A.
L1Cache
Indicates a relationship where data or instructions are stored or accessed in the first-level (closest, fastest) cache memory associated with a processor core.
-
B.
instructionCacheSize
Indicates the size or capacity of the instruction cache associated with a processor or computing component.
-
C.
L2Cache
Indicates that one entity functions as a level-2 cache for another, storing intermediate data or results to speed up repeated access or computation.
-
D.
hasMemorySlot
Indicates that an entity possesses a specific memory slot or storage location for holding information or data.
-
E.
requiresSupportChips
Indicates that an entity depends on or needs additional support components (chips) in order to function or be used properly.
- 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_69ca83ee26cc81909ac624e190597d6d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cd03edd37481908ea2f6dac354f04f |
completed | April 1, 2026, 11:39 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4765648190aa9445c4a22dc471 |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc95597be081908ece2491dd2f0f74 |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:30 p.m.