Triple
T14595199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3rd Marine Logistics Group Headquarters Regiment |
E342541
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | headquarters and service regiment |
C35001
|
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: headquarters and service regiment Context triple: [3rd Marine Logistics Group Headquarters Regiment, instanceOf, headquarters and service regiment]
-
A.
corps artillery headquarters
A corps artillery headquarters is the command element responsible for planning, coordinating, and controlling all artillery and fire support operations within a military corps.
-
B.
headquarters
The headquarters is the primary location where an organization’s central management, strategic decision-making, and key administrative functions are coordinated and controlled.
-
C.
deployable corps-level headquarters
A deployable corps-level headquarters is a mobile, command-and-control organization capable of planning, coordinating, and directing large-scale, multi-division military operations across a theater of operations.
-
D.
Wehrmacht headquarters
The Wehrmacht headquarters was the central command authority of Nazi Germany's unified armed forces, responsible for strategic planning, coordination, and direction of military operations during World War II.
-
E.
military administrative corps
A military administrative corps is a specialized branch of the armed forces responsible for managing personnel, logistics, finance, records, and other support functions that enable effective military operations.
- 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:25 a.m.