Triple
T21627441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AY-3-8912 |
E533738
|
entity |
| Predicate | channelMixing |
P145285
|
FINISHED |
| Object | stereo possible via external wiring |
—
|
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: stereo possible via external wiring | Statement: [AY-3-8912, channelMixing, stereo possible via external wiring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: channelMixing Context triple: [AY-3-8912, channelMixing, stereo possible via external wiring]
-
A.
mixingMethod
Indicates the technique or process used to combine multiple components or substances into a uniform mixture.
-
B.
mixingFocus
Indicates that an action or process centers on combining or blending multiple elements, emphasizing the act of mixing as the primary focus.
-
C.
mixingStyle
Indicates how two or more elements are combined or blended together in a particular manner or technique.
-
D.
mixesElement
Indicates that one entity combines or blends another entity or element into a mixture or composite.
-
E.
mixType
Indicates that one entity is combined or blended with another in a particular manner or category of mixing.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef52141e1c8190a861f4bc7cfcb490 |
completed | April 27, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69cb4bcbc8190a4fc2d508df107be |
completed | April 20, 2026, 9:37 p.m. |
Created at: April 16, 2026, 6:34 p.m.