Triple
T29423148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 11 Supply and Transport Company |
E746208
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transport company (military) |
C55589
|
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: transport company (military) Context triple: [11 Supply and Transport Company, instanceOf, transport company (military)]
-
A.
military air transport organization
A military air transport organization is a structured entity responsible for planning, coordinating, and executing the airlift of personnel, equipment, and supplies to support military operations and strategic objectives.
-
B.
transportation services company
A transportation services company is an organization that plans, manages, and operates the movement of people or goods using various modes of transport, such as road, rail, air, or sea, often providing logistics, scheduling, and support services.
-
C.
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.
-
D.
military logistics enterprise
A military logistics enterprise is an organization that plans, coordinates, and executes the procurement, transportation, storage, and distribution of resources to ensure armed forces are supplied and operationally ready.
-
E.
tactical military truck
A tactical military truck is a rugged, all-terrain vehicle designed to transport troops, equipment, and supplies in combat and support operations under harsh and hostile conditions.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 3:07 p.m.