Triple
T16501086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AM |
E400799
|
entity |
| Predicate | signalFormat |
P55008
|
FINISHED |
| Object | double-sideband with carrier |
—
|
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: double-sideband with carrier | Statement: [AM, signalFormat, double-sideband with carrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalFormat Context triple: [AM, signalFormat, double-sideband with carrier]
-
A.
sensorFormat
Indicates the data encoding or representation standard used by a sensor to output its measurements.
-
B.
detectorFormat
Indicates the specific data or signal representation used by a detector to encode or output its measurements.
-
C.
signalContent
Indicates that one entity is the informational content or message carried, conveyed, or represented by a signal produced or transmitted by another entity.
-
D.
signalProperty
chosen
Indicates that one entity has a specific characteristic, attribute, or feature related to a signal.
-
E.
protocolIdentifierFormat
Indicates how a protocol’s identifier is structured or formatted.
- 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_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. |
Created at: April 10, 2026, 5:14 a.m.