Triple
T385661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE MTT-S International Microwave Symposium |
E8775
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | microwave engineering conference |
C2167
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: microwave engineering conference Context triple: [IEEE MTT-S International Microwave Symposium, instanceOf, microwave engineering conference]
-
A.
radio engineer
A radio engineer is a professional who designs, develops, tests, and maintains radio frequency systems and equipment used for wireless communication and broadcasting.
-
B.
wireless communication device
A wireless communication device is an electronic apparatus that transmits and receives data over radio or other non-wired signals to enable voice, text, or multimedia communication without physical connections.
-
C.
heterodyne receiver
A heterodyne receiver is a radio receiver that converts an incoming signal to an intermediate frequency by mixing it with a locally generated oscillator signal to enable easier and more selective amplification and filtering.
-
D.
engineering journal
An engineering journal is a periodical publication that presents peer-reviewed research, technical developments, and practical applications in various fields of engineering.
-
E.
division of IEEE
A division of IEEE is a specialized organizational unit within the Institute of Electrical and Electronics Engineers that focuses on advancing a particular technical field or professional area through standards, publications, conferences, and member activities.
- F. None of above. chosen
Provenance (1 batch)
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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.