Triple
T25808312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LP record |
E650032
|
entity |
| Predicate | signalConversion |
P39633
|
FINISHED |
| Object | mechanical-to-electrical transduction |
—
|
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: mechanical-to-electrical transduction | Statement: [LP record, signalConversion, mechanical-to-electrical transduction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalConversion Context triple: [LP record, signalConversion, mechanical-to-electrical transduction]
-
A.
digitalSignal
Indicates that the relationship or action involves representing, transmitting, or processing information as a discrete-time, discrete-value (digital) signal between entities.
-
B.
signalReception
Indicates the reception or detection of a transmitted signal by a receiving entity.
-
C.
signalVoltage
Indicates the electrical potential level carried by a signal in a circuit or communication channel.
-
D.
conversionProcess
chosen
Indicates a process in which something is transformed or changed from one state, form, or representation into another.
-
E.
conversionEvent
Indicates that a user or entity has completed a desired target action (such as a purchase, signup, or other goal) that counts as a successful conversion.
- 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f600c2a7748190809b59109e476169 |
completed | May 2, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 7:06 a.m.