Triple
T36084557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armed Forces Radio and Television Service |
E1043739
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military broadcasting service |
C409
|
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: military broadcasting service Context triple: [Armed Forces Radio and Television Service, instanceOf, military broadcasting service]
-
A.
radio broadcast service
A radio broadcast service is a system that transmits audio content over radio frequencies from a central source to multiple receivers within a defined coverage area.
-
B.
public service broadcasting
Public service broadcasting is a media system, typically funded by the public or through license fees, that provides impartial, high-quality content designed to inform, educate, and entertain while serving the democratic, cultural, and social needs of society rather than commercial interests.
-
C.
military communications organization
chosen
A military communications organization is a structured unit responsible for planning, managing, and operating secure, reliable information and communication systems that support command, control, and coordination of military forces.
-
D.
broadcasting ministry
A broadcasting ministry is a religious organization or department that uses radio, television, and digital media to communicate spiritual messages, services, and teachings to a broad audience.
-
E.
military signal
A military signal is a transmitted message, visual cue, or coded communication used by armed forces to convey orders, information, or intentions in a coordinated and secure manner.
- F. None of above.
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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.