Triple
T4360711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Home Intelligence reports |
E98653
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | wartime assessment |
C15799
|
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: wartime assessment Context triple: [Home Intelligence reports, instanceOf, wartime assessment]
-
A.
wartime agency
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.
wartime settlement
A wartime settlement is an agreement or arrangement reached during or immediately after armed conflict that defines the terms for ending hostilities, addressing territorial or political disputes, and establishing conditions for postwar order.
-
C.
wartime codename
A wartime codename is a deliberately chosen, often cryptic label used to conceal the true nature, identity, or objectives of military operations, units, technologies, or locations during conflict.
-
D.
wartime economic control law
A wartime economic control law is a legal framework that grants governments special powers during armed conflict to regulate, direct, and restrict economic activities, resources, and markets in support of national defense and war objectives.
-
E.
wartime economic control law
A wartime economic control law is a legal framework that grants governments special powers during armed conflict to regulate, direct, and restrict economic activities, resources, and markets in support of national defense and security objectives.
- 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:16 p.m.