Triple
T22973620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM 1401, A User’s Manual |
E571253
|
entity |
| Predicate | usesSoundSources |
P41641
|
FINISHED |
| Object | vintage computer sounds |
—
|
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: vintage computer sounds | Statement: [IBM 1401, A User’s Manual, usesSoundSources, vintage computer sounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSoundSources Context triple: [IBM 1401, A User’s Manual, usesSoundSources, vintage computer sounds]
-
A.
usesSoundDevice
Indicates that one entity operates or relies on a sound-producing or sound-processing device in relation to another entity or context.
-
B.
containsSound
Indicates that one entity includes, embodies, or produces the sound associated with another entity.
-
C.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
-
D.
usesAudioFrom
chosen
Indicates that one entity incorporates or relies on the audio content produced or provided by another entity.
-
E.
hasExperimentalSound
Indicates that something possesses or exhibits an unconventional, innovative, or avant-garde sound quality or style.
- 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_69e245b2c6548190a0e4c7f2f7df2d48 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182350b448190a34e5fa0167fd964 |
completed | April 29, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:48 p.m.