Triple
T11520707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Power Macintosh G4 (AGP Graphics) |
E273153
|
entity |
| Predicate | graphicsBus |
P31273
|
FINISHED |
| Object | AGP 2x |
—
|
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: AGP 2x | Statement: [Power Macintosh G4 (AGP Graphics), graphicsBus, AGP 2x]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: graphicsBus Context triple: [Power Macintosh G4 (AGP Graphics), graphicsBus, AGP 2x]
-
A.
graphicsAdapter
Indicates a relationship where a device or system is associated with, uses, or is equipped with a particular graphics adapter (graphics processing hardware).
-
B.
systemBus
Indicates a relationship where a component is connected to or communicates over a shared system-wide communication bus.
-
C.
graphicsAPI
Indicates a relationship where one entity uses, supports, or is implemented with a particular graphics application programming interface (graphicsAPI).
-
D.
expansionBus
chosen
Indicates a hardware connection through which a device can be attached to or communicate over an expansion bus.
-
E.
graphicsType
Indicates the type or category of graphics associated with or used by an 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d87fd129c88190893b95222480e04a |
completed | April 10, 2026, 4:42 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.