Triple
T35290900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macintosh Performa 578 |
E1019220
|
entity |
| Predicate | audioInOutPorts |
P33360
|
FINISHED |
| Object | 3.5 mm jacks |
—
|
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: 3.5 mm jacks | Statement: [Macintosh Performa 578, audioInOutPorts, 3.5 mm jacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioInOutPorts Context triple: [Macintosh Performa 578, audioInOutPorts, 3.5 mm jacks]
-
A.
audioPorts
chosen
Indicates that one entity provides or is equipped with audio input/output ports that can be used or connected by the other entity.
-
B.
midiPorts
Indicates a relationship where one entity exposes or uses one or more MIDI input/output ports associated with another entity.
-
C.
hasMicrophonePort
Indicates that an entity includes or provides a dedicated connection point for attaching a microphone.
-
D.
audioChip
Indicates that one entity functions as, or contains, an audio processing chip in relation to another entity.
-
E.
audioStack
Indicates that one audio element is layered or queued on top of another within an ordered audio sequence or mix.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79013a2308190a13818632a697230 |
completed | May 3, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.