Triple
T31395607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bose 901 loudspeaker system |
E800855
|
entity |
| Predicate | typicalImpedance |
P44393
|
FINISHED |
| Object | 8 ohms |
—
|
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: 8 ohms | Statement: [Bose 901 loudspeaker system, typicalImpedance, 8 ohms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalImpedance Context triple: [Bose 901 loudspeaker system, typicalImpedance, 8 ohms]
-
A.
hasInputImpedanceTypical
chosen
Indicates that something is characterized by a typical or standard value of input impedance in a given context.
-
B.
hasImpedance
Indicates that one entity possesses or is characterized by a specific electrical impedance value or property in relation to another.
-
C.
cableImpedance
Indicates the electrical opposition (impedance) presented by a cable to alternating current flow in a circuit.
-
D.
terminatorImpedance
Indicates the electrical impedance value associated with a terminator used to terminate a signal line or transmission path.
-
E.
gateInputImpedance
Indicates the electrical input impedance presented at the gate terminal of a device relative to a driving source.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:19 p.m.