Triple
T29181939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tandy 1000 series (compatible PSG) |
E739766
|
entity |
| Predicate | soundHardwareType |
P44235
|
FINISHED |
| Object | programmable sound generator |
—
|
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: programmable sound generator | Statement: [Tandy 1000 series (compatible PSG), soundHardwareType, programmable sound generator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soundHardwareType Context triple: [Tandy 1000 series (compatible PSG), soundHardwareType, programmable sound generator]
-
A.
soundHardware
chosen
Indicates that an entity is associated with, uses, or provides sound-related hardware components or capabilities.
-
B.
soundboardType
Indicates the specific category or configuration of a soundboard associated with an entity.
-
C.
audioChip
Indicates that one entity functions as, or contains, an audio processing chip in relation to another entity.
-
D.
hasSoundEngineType
Indicates a relationship where an entity is associated with or characterized by a specific type of sound engine.
-
E.
soundSpecialization
Indicates a relationship where one entity’s role, function, or expertise is specifically focused on sound (e.g., its production, design, or manipulation) 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_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 11:57 a.m.