Triple
T37105477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Team Encounter |
E918827
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | radio enthusiast organization |
C64612
|
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: radio enthusiast organization Context triple: [Team Encounter, instanceOf, radio enthusiast organization]
-
A.
radio hobbyist magazine
A radio hobbyist magazine is a periodical publication that provides enthusiasts with news, technical articles, project guides, equipment reviews, and community information related to amateur and hobby radio activities.
-
B.
amateur radio magazine
An amateur radio magazine is a periodical publication that provides hobbyist radio operators with technical articles, equipment reviews, operating tips, regulatory updates, and community news related to amateur (ham) radio.
-
C.
amateur radio event
An amateur radio event is a planned gathering or activity where licensed radio enthusiasts communicate, demonstrate equipment, or participate in contests and public service operations using allocated radio frequencies.
-
D.
radio engineering company
A radio engineering company specializes in the design, development, testing, and maintenance of radio frequency systems and communication technologies for commercial, industrial, or governmental applications.
-
E.
radio engineering magazine
A radio engineering magazine is a periodical publication that provides technical articles, industry news, designs, and practical guidance related to radio frequency systems, wireless communication, and associated electronic technologies.
- 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.