Triple
T33321685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conference Support Program for Developing Countries |
E853153
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | logistical support program |
C39103
|
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: logistical support program Context triple: [Conference Support Program for Developing Countries, instanceOf, logistical support program]
-
A.
logistics support program
chosen
A logistics support program is a coordinated set of processes, resources, and tools designed to plan, manage, and sustain the efficient movement, storage, and maintenance of materials and services throughout their lifecycle.
-
B.
logistical support office
A logistical support office is an organizational unit responsible for planning, coordinating, and managing the movement, storage, and distribution of resources, equipment, and services to ensure smooth operational support.
-
C.
military logistics software system
A military logistics software system is an integrated digital platform that plans, tracks, and optimizes the movement, supply, maintenance, and readiness of military resources across operations and theaters.
-
D.
logistical operation
A logistical operation is a coordinated set of activities and processes that plan, implement, and control the efficient movement and storage of goods, information, or resources from origin to destination.
-
E.
military assistance program
A military assistance program is an organized initiative through which one nation or entity provides training, equipment, funding, or advisory support to strengthen the defense capabilities of another.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:33 a.m.