Triple
T30053223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Region Legal Service Offices |
E763657
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military legal services organization |
C55338
|
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 legal services organization Context triple: [Region Legal Service Offices, instanceOf, military legal services organization]
-
A.
military lawyer
A military lawyer is a legal professional who provides counsel, representation, and guidance on military law, regulations, and justice within the armed forces.
-
B.
military support organization
A military support organization is an entity that provides logistical, administrative, technical, and welfare services to enable and sustain the effective operation of armed forces.
-
C.
military organization
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.
-
D.
military justice authority
chosen
A military justice authority is an official body or position within the armed forces responsible for administering, overseeing, and enforcing laws, regulations, and disciplinary procedures applicable to military personnel.
-
E.
military logistics directorate
A military logistics directorate is an organizational unit responsible for planning, coordinating, and managing the procurement, storage, movement, and maintenance of supplies, equipment, and services that sustain armed forces operations.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 6:56 p.m.