Triple
T30405369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PowerPC-to-Intel Mac architecture transition |
E773462
|
entity |
| Predicate | newProcessorVendor |
P61346
|
FINISHED |
| Object | Intel |
—
|
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: Intel | Statement: [PowerPC-to-Intel Mac architecture transition, newProcessorVendor, Intel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: newProcessorVendor Context triple: [PowerPC-to-Intel Mac architecture transition, newProcessorVendor, Intel]
-
A.
architectureVendor
Indicates that one entity serves as the provider or supplier of architectural services, solutions, or products to another entity.
-
B.
technologyVendor
Indicates that one entity serves as the provider or supplier of technology products or services to another entity.
-
C.
osVendor
Indicates that one entity is the vendor or provider of an operating system associated with another entity.
-
D.
usesProcessorBrand
Indicates that one entity employs or is built with a processor manufactured by the specified brand.
-
E.
CPUVendor
chosen
Indicates that a given CPU is manufactured or branded by a particular vendor.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6861d69a08190802564e3aa7d6ea7 |
completed | May 2, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:03 p.m.