Triple
T21674339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tele |
E534928
|
entity |
| Predicate | hasOutputJackLocation |
P33360
|
FINISHED |
| Object | side-mounted jack cup |
—
|
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: side-mounted jack cup | Statement: [Tele, hasOutputJackLocation, side-mounted jack cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutputJackLocation Context triple: [Tele, hasOutputJackLocation, side-mounted jack cup]
-
A.
audioJackType
Indicates the specific kind or standard of audio jack interface used or supported in the relationship.
-
B.
hasOutputImpedance
Indicates that an entity (such as a device or component) exhibits a specific impedance at its output terminals.
-
C.
hasStereoOutput
Indicates that an entity provides or supports audio output in stereo (two-channel) format.
-
D.
hasSerialOutputPin
Indicates that an entity is equipped with a pin or connector dedicated to transmitting data via a serial output interface.
-
E.
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.
- 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_69e0c46898008190aa618a4af55bd1ee |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef8a0ed5388190b8f1932fb3f11c6a |
completed | April 27, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:41 p.m.