Triple
T29456568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HAM-8 display mode |
E747117
|
entity |
| Predicate | introducedOnHardware |
P29731
|
FINISHED |
| Object | Amiga AGA chipset |
—
|
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: Amiga AGA chipset | Statement: [HAM-8 display mode, introducedOnHardware, Amiga AGA chipset]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedOnHardware Context triple: [HAM-8 display mode, introducedOnHardware, Amiga AGA chipset]
-
A.
introducedHardware
Indicates that an entity caused a particular piece of hardware to be brought into use or made available for the first time.
-
B.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
-
C.
introducedInProduct
chosen
Indicates that something (such as a feature, component, or concept) first appeared or was initially made available within a particular product.
-
D.
introducedInSystem
Indicates that an entity was first added, implemented, or made available within a particular system.
-
E.
previouslySupportedHardware
Indicates that the subject hardware was supported in the past but is no longer currently supported.
- 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_69f0bd4125f88190b56104591351619c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 28, 2026, 3:46 p.m.