Triple
T31620769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ministry of War Transport |
E806888
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | war-time government ministry |
C236
|
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: war-time government ministry Context triple: [Ministry of War Transport, instanceOf, war-time government ministry]
-
A.
wartime agency
chosen
A wartime agency is an organization, typically governmental or intergovernmental, established or empowered during armed conflict to coordinate military, economic, and civilian efforts in support of war objectives.
-
B.
government ministry
A government ministry is a specialized administrative department within a government, headed by a minister, responsible for formulating and implementing public policies in a specific sector such as health, education, or finance.
-
C.
Soviet government ministry
A Soviet government ministry was a centralized state administrative body responsible for directing and managing a specific sector of the economy, society, or state functions under the authority of the USSR’s Communist Party leadership.
-
D.
wartime entity
A wartime entity is an organized group, institution, or structure that operates within or because of armed conflict, influencing or participating in military, political, economic, or social aspects of war.
-
E.
military government function
A military government function is an activity or responsibility carried out by armed forces to administer, control, or support governance and public order, especially in times of conflict, occupation, or emergency.
- 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:41 p.m.