Triple
T32360471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PowerPC ISA v2.0 |
E826848
|
entity |
| Predicate | usedByProcessorFamily |
P12004
|
FINISHED |
| Object | IBM POWER4 |
—
|
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: IBM POWER4 | Statement: [PowerPC ISA v2.0, usedByProcessorFamily, IBM POWER4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByProcessorFamily Context triple: [PowerPC ISA v2.0, usedByProcessorFamily, IBM POWER4]
-
A.
introducedByProcessorFamily
Indicates that one entity was brought into existence, use, or context by a specific processor family.
-
B.
supportsProcessorFamily
Indicates that one entity (such as hardware or software) is compatible with and can operate using a specified processor family.
-
C.
usesProcessorSeries
chosen
Indicates that one entity operates using, or is built to run on, a specific series or family of processors.
-
D.
usedByFamilyOf
Indicates that something is utilized or consumed by members of a particular family or household.
-
E.
introducedByProcessor
Indicates that something was created, added, or brought into a system as a result of actions performed by a specific processor.
- 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 1, 2026, 12:49 a.m.