Triple
T38566184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Power Macintosh 7300 |
E928222
|
entity |
| Predicate | videoArchitecture |
P11219
|
FINISHED |
| Object | PCI-based graphics |
—
|
LITERAL FINISHED |
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: PCI-based graphics | Statement: [Power Macintosh 7300, videoArchitecture, PCI-based graphics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: videoArchitecture Context triple: [Power Macintosh 7300, videoArchitecture, PCI-based graphics]
-
A.
graphicsArchitecture
chosen
Indicates the underlying design or structural framework that defines how a system’s graphics or visual rendering components are organized and operate.
-
B.
renderingArchitecture
Indicates the specific rendering system or framework used to generate visual output for a given entity or environment.
-
C.
exampleArchitecture
Indicates that one entity serves as a representative or illustrative instance of the architectural style, structure, or design of another entity.
-
D.
toArchitecture
Indicates a relationship in which something is designed, structured, or organized according to a particular architectural style, plan, or system.
-
E.
architecture
Indicates the structural design or organizational framework that defines how components of a system or entity are arranged and interact.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.