Triple
T23022702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MR IV (South Vietnam) |
E573210
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative military district |
C13035
|
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: administrative military district Context triple: [MR IV (South Vietnam), instanceOf, administrative military district]
-
A.
military administrative division
chosen
A military administrative division is a geographically defined area organized under a specific command structure to manage, coordinate, and support military operations, logistics, and governance within its boundaries.
-
B.
military administration
Military administration is the organizational and managerial framework responsible for planning, directing, and overseeing the personnel, resources, logistics, and policies that enable a military force to function effectively.
-
C.
German military district
A German military district is a regional administrative and organizational unit of the German armed forces responsible for local command, logistics, personnel management, and military infrastructure within its designated area.
-
D.
military-controlled zone
A military-controlled zone is a designated geographic area where military authorities exercise primary control over security, movement, and activities, often restricting civilian access and enforcing special regulations.
-
E.
naval district
A naval district is a geographically defined administrative area of a navy responsible for organizing, supporting, and overseeing naval operations, personnel, and facilities within its boundaries.
- 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_69e245b821008190b0e09cb02092aae1 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:52 p.m.