Triple
T37455564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple UniNorth |
E930789
|
entity |
| Predicate | targetCPUFamily |
P11217
|
FINISHED |
| Object | PowerPC G4 |
—
|
NE NERFINISHED |
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: PowerPC G4 | Statement: [Apple UniNorth, targetCPUFamily, PowerPC G4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetCPUFamily Context triple: [Apple UniNorth, targetCPUFamily, PowerPC G4]
-
A.
cpuFamily
chosen
Indicates that one CPU belongs to, or is categorized under, a particular CPU family or architecture lineage.
-
B.
firstSupportedCPUFamily
Indicates the earliest CPU family that a system, software, or feature is designed to support or is compatible with.
-
C.
CPUType
Indicates the specific model or category of processor architecture that an entity uses or is associated with.
-
D.
baseCPUVariantName
Indicates that one CPU model is the fundamental or original variant from which another CPU model is derived or named.
-
E.
integratedGPUFamily
Indicates that one entity is a member of, or associated with, a particular family or series of integrated graphics processing units.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: May 3, 2026, 4:17 p.m.