Triple
T12152499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 555th Medical Company (Area Support) |
E289490
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military medical company |
C22289
|
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 medical company Context triple: [555th Medical Company (Area Support), instanceOf, military medical company]
-
A.
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.
-
B.
U.S. Army medical unit
chosen
A U.S. Army medical unit is a military organization that provides coordinated medical care, treatment, evacuation, and health support to soldiers and authorized personnel in both garrison and deployed operational environments.
-
C.
defense company
A defense company is an organization that designs, develops, manufactures, and supports military and security-related products, technologies, and services for governments and authorized entities.
-
D.
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.
-
E.
private military contractor team
A private military contractor team is a coordinated group of hired security and combat specialists who provide military-style services—such as protection, training, and tactical operations—for governments, corporations, or other clients under contractual agreements.
- 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_69d6ab4c6710819097a9d228382dde43 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:49 p.m.