Triple
T30405341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PowerPC-to-Intel Mac architecture transition |
E773462
|
entity |
| Predicate | fromArchitecture |
P85958
|
FINISHED |
| Object | PowerPC |
—
|
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 | Statement: [PowerPC-to-Intel Mac architecture transition, fromArchitecture, PowerPC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fromArchitecture Context triple: [PowerPC-to-Intel Mac architecture transition, fromArchitecture, PowerPC]
-
A.
exampleArchitecture
Indicates that one entity serves as a representative or illustrative instance of the architectural style, structure, or design of another entity.
-
B.
architectureName
Indicates the specific name or title assigned to an architecture.
-
C.
previousArchitecture
chosen
Indicates that one architecture served as the predecessor or earlier version of another architecture in a sequence or evolution.
-
D.
derivedFromArchitecture
Indicates that something originates from, is based on, or is developed using a particular architectural design or framework.
-
E.
usesArchitecture
Indicates that one entity is built, implemented, or operates according to the architectural style, framework, or design specified by another entity.
- 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.