Triple
T16501076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AM |
E400799
|
entity |
| Predicate | demodulatedBy |
P123792
|
FINISHED |
| Object | envelope detector |
—
|
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: envelope detector | Statement: [AM, demodulatedBy, envelope detector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demodulatedBy Context triple: [AM, demodulatedBy, envelope detector]
-
A.
decipheredFrom
Indicates that something has been interpreted, decoded, or understood based on information derived from another source.
-
B.
usesModulation
Indicates that one entity applies or employs a particular modulation method or scheme in relation to another entity or process.
-
C.
dismantledBy
Indicates that something has been taken apart, disassembled, or broken down by a particular agent or entity.
-
D.
demonstratedBy
Indicates that something is shown, proven, or made evident through the actions, behavior, or example of a particular entity.
-
E.
definesModulation
Indicates that one entity specifies or determines how another entity is modulated or altered in its behavior, intensity, or effect.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e4ddc88819081fedb726add3e96 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:14 a.m.