Triple
T14161445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Coast Guard |
E350955
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | armed service |
C298
|
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: armed service Context triple: [United States Coast Guard, instanceOf, armed service]
-
A.
branch of service
A branch of service is a distinct organizational subdivision within a nation’s armed forces or public service, defined by its specific mission, capabilities, and operational domain.
-
B.
military system
A military system is an organized structure of personnel, equipment, doctrines, and processes designed to plan, conduct, and support defense and combat operations.
-
C.
auxiliary military force
An auxiliary military force is a supplementary, often non-regular or part-time armed organization that supports a nation’s primary military through additional manpower, specialized skills, or local defense roles.
-
D.
military organization
chosen
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
-
E.
military-adjacent uniformed service
A military-adjacent uniformed service is an organized, government-sanctioned body whose members wear standardized uniforms and perform defense-, security-, or support-related functions alongside or in coordination with the armed forces, but are not formally part of the military.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 12:59 a.m.