Triple
T19451615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lightning EarPods |
E486624
|
entity |
| Predicate | hasImpedance |
P135960
|
FINISHED |
| Object | similar to 3.5 mm EarPods |
—
|
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: similar to 3.5 mm EarPods | Statement: [Lightning EarPods, hasImpedance, similar to 3.5 mm EarPods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImpedance Context triple: [Lightning EarPods, hasImpedance, similar to 3.5 mm EarPods]
-
A.
hasOutputImpedance
Indicates that an entity (such as a device or component) exhibits a specific impedance at its output terminals.
-
B.
hasInputImpedanceTypical
Indicates that something is characterized by a typical or standard value of input impedance in a given context.
-
C.
cableImpedance
Indicates the electrical opposition (impedance) presented by a cable to alternating current flow in a circuit.
-
D.
gateInputImpedance
Indicates the electrical input impedance presented at the gate terminal of a device relative to a driving source.
-
E.
hasInterference
Indicates that one entity negatively affects or obstructs the normal function, performance, or occurrence of another entity or process.
- F. None of above. chosen
Provenance (4 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63392aab08190aab09b7c356e5b10 |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:38 p.m.