Triple
T12755314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macintosh Performa 6200 |
E304843
|
entity |
| Predicate | hasCPUType |
P98650
|
FINISHED |
| Object | RISC |
—
|
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: RISC | Statement: [Macintosh Performa 6200, hasCPUType, RISC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCPUType Context triple: [Macintosh Performa 6200, hasCPUType, RISC]
-
A.
CPUType
chosen
Indicates the specific model or category of processor architecture that an entity uses or is associated with.
-
B.
hasCPUCore
Indicates that an entity (typically a computing device or processor) possesses or includes a specific CPU core as one of its components.
-
C.
hasPlatformType
Indicates that an entity is associated with or characterized by a specific type or category of platform.
-
D.
cpuFamily
Indicates that one CPU belongs to, or is categorized under, a particular CPU family or architecture lineage.
-
E.
hasSoftwareType
Indicates that an entity is associated with or classified under a particular type or category of software.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d8b57b88190b29b8fdca415c81c |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:27 p.m.