Triple
T30405367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PowerPC-to-Intel Mac architecture transition |
E773462
|
entity |
| Predicate | replacedProcessorVendor |
P188788
|
FINISHED |
| Object | IBM |
—
|
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 | Statement: [PowerPC-to-Intel Mac architecture transition, replacedProcessorVendor, IBM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedProcessorVendor Context triple: [PowerPC-to-Intel Mac architecture transition, replacedProcessorVendor, IBM]
-
A.
replacedProcess
Indicates that one process has been substituted or superseded by another process.
-
B.
architectureVendor
Indicates that one entity serves as the provider or supplier of architectural services, solutions, or products to another entity.
-
C.
replacedPlatform
Indicates that one platform has been superseded or taken over by another platform.
-
D.
replacedOnPlatformBy
Indicates that one entity has been superseded or taken over by another entity on a particular platform.
-
E.
osVendor
Indicates that one entity is the vendor or provider of an operating system associated with another entity.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbad1b3ba08190ad69e21461333f2e |
completed | May 6, 2026, 9:05 p.m. |
Created at: April 29, 2026, 8:03 p.m.