Triple
T11960777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 8110 4G |
E284662
|
entity |
| Predicate | audioPort |
P33360
|
FINISHED |
| Object | 3.5 mm headphone jack |
—
|
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 headphone jack | Statement: [Nokia 8110 4G, audioPort, 3.5 mm headphone jack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioPort Context triple: [Nokia 8110 4G, audioPort, 3.5 mm headphone jack]
-
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.
audioChip
Indicates that one entity functions as, or contains, an audio processing chip in relation to another entity.
-
D.
audioChannels
Indicates the number or configuration of distinct audio signal paths (such as mono, stereo, or surround) used in a recording, transmission, or playback.
-
E.
supportsAudioReturnChannel
Indicates that one entity is capable of handling an audio return channel from another entity, allowing audio to be sent back over the same connection.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9036941948190b150369094551731 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.