Triple
T29181938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tandy 1000 series (compatible PSG) |
E739766
|
entity |
| Predicate | soundHardwareCompatibility |
P34359
|
FINISHED |
| Object | Texas Instruments SN76489 |
—
|
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: Texas Instruments SN76489 | Statement: [Tandy 1000 series (compatible PSG), soundHardwareCompatibility, Texas Instruments SN76489]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soundHardwareCompatibility Context triple: [Tandy 1000 series (compatible PSG), soundHardwareCompatibility, Texas Instruments SN76489]
-
A.
soundHardware
Indicates that an entity is associated with, uses, or provides sound-related hardware components or capabilities.
-
B.
hasHardwareCompatibilityWith
chosen
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
-
C.
usesSoundDevice
Indicates that one entity operates or relies on a sound-producing or sound-processing device in relation to another entity or context.
-
D.
supportsPCM
Indicates that one entity is capable of handling, processing, or is compatible with PCM (Pulse-Code Modulation) audio data used by another entity.
-
E.
audioChip
Indicates that one entity functions as, or contains, an audio processing chip in relation to 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f66384473c81909fb9ff9037f56b67 |
completed | May 2, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 11:57 a.m.