Triple
T29456569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HAM-8 display mode |
E747117
|
entity |
| Predicate | requiresChipset |
P78306
|
FINISHED |
| Object | AGA |
—
|
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: AGA | Statement: [HAM-8 display mode, requiresChipset, AGA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresChipset Context triple: [HAM-8 display mode, requiresChipset, AGA]
-
A.
requiresSupportChips
chosen
Indicates that an entity depends on or needs additional support components (chips) in order to function or be used properly.
-
B.
usedWithChipsetsFrom
Indicates that something is designed or suitable to be used together with specific chipsets from a given manufacturer or family.
-
C.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
-
D.
hasChipType
Indicates that an entity is associated with or uses a specific type or category of chip.
-
E.
requiresFirmware
Indicates that one entity depends on specific firmware being present or installed on another entity in order to function or be valid.
- 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_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: April 28, 2026, 3:46 p.m.