Triple
T4265622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defense Transportation System |
E96817
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military transportation system |
C8693
|
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 transportation system Context triple: [Defense Transportation System, instanceOf, military transportation system]
-
A.
cargo militar
Cargo militar es una posición o función oficial dentro de una organización de defensa o fuerzas armadas, caracterizada por responsabilidades jerárquicas, operativas y administrativas específicas en el ámbito militar.
-
B.
military system
A military system is an organized structure of personnel, equipment, doctrines, and processes designed to plan, conduct, and support defense and combat operations.
-
C.
military air transport organization
chosen
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.
-
D.
military equipment
Military equipment comprises the specialized weapons, vehicles, protective gear, communication systems, and support tools designed, produced, and used by armed forces to conduct and support combat and defense operations.
-
E.
truck-mounted artillery system
A truck-mounted artillery system is a mobile weapons platform that integrates heavy artillery guns or rocket launchers onto a wheeled truck chassis to provide rapid, long-range fire support with high strategic and tactical mobility.
- 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_69b34543f06c8190915ebb1a4574ffa9 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:07 p.m.