Triple
T12728399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macintosh Performa 600 |
E304165
|
entity |
| Predicate | audioIn |
P83355
|
FINISHED |
| Object | stereo 8-bit |
—
|
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: stereo 8-bit | Statement: [Macintosh Performa 600, audioIn, stereo 8-bit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioIn Context triple: [Macintosh Performa 600, audioIn, stereo 8-bit]
-
A.
soundRecordingBy
Indicates that a sound recording was created, performed, or produced by a particular agent (such as an artist, band, or producer).
-
B.
audioChip
Indicates that one entity functions as, or contains, an audio processing chip in relation to another entity.
-
C.
usesAudioFrom
Indicates that one entity incorporates or relies on the audio content produced or provided by another entity.
-
D.
audioStandard
chosen
Indicates the audio format or specification standard that applies to the associated media or device.
-
E.
hasSpeech
Indicates that an entity produces, delivers, or is associated with a spoken utterance or verbal expression.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:25 p.m.