Triple
T9632311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HP 200A audio oscillator |
E232836
|
entity |
| Predicate | distortionCharacteristic |
P662
|
FINISHED |
| Object | low total harmonic distortion |
—
|
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: low total harmonic distortion | Statement: [HP 200A audio oscillator, distortionCharacteristic, low total harmonic distortion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distortionCharacteristic Context triple: [HP 200A audio oscillator, distortionCharacteristic, low total harmonic distortion]
-
A.
hasAberrationCharacteristics
Indicates that an entity exhibits traits or properties that deviate from what is considered normal, standard, or expected.
-
B.
dataCharacteristic
Indicates that one entity specifies a property, attribute, or feature that characterizes a given piece of data.
-
C.
characterizedBy
chosen
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
D.
vocalizationCharacteristic
Indicates how an entity’s vocal sounds are characterized, such as their quality, style, or distinctive acoustic features.
-
E.
catalogCharacteristic
Indicates that a catalog has a specific characteristic or attribute associated with it.
- 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_69ca848940cc8190b97cec654cb3bb4a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b2783b48190a9929dc3e3cd2956 |
completed | April 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:11 p.m.