Triple
T16918047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Service Corps |
E410370
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military logistics branch |
C13448
|
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 logistics branch Context triple: [Service Corps, instanceOf, military logistics branch]
-
A.
logistics brigade
A logistics brigade is a military unit responsible for planning, coordinating, and executing the supply, transportation, maintenance, and support services needed to sustain combat and support forces.
-
B.
branch of the United States Army
A branch of the United States Army is a specialized functional category, such as Infantry or Signal Corps, that organizes soldiers, training, and equipment around a distinct mission set and expertise area within the Army.
-
C.
Marine Air-Ground Task Force logistics element
The Marine Air-Ground Task Force logistics element is the component responsible for providing comprehensive combat service support—including supply, maintenance, transportation, health services, and engineering—to sustain the MAGTF’s operations across all domains.
-
D.
military support organization
chosen
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.
-
E.
military medical branch
A military medical branch is the specialized division of a nation's armed forces responsible for providing healthcare, medical support, and emergency treatment to military personnel in both peacetime and combat 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:30 a.m.