Triple
T9277964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Voters Act |
E222997
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | wartime elections law |
C1710
|
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 elections law Context triple: [Military Voters Act, instanceOf, wartime elections law]
-
A.
election law
chosen
Election law is the body of legal rules and principles that governs how elections are conducted, including voter eligibility, campaign practices, ballot access, vote counting, and the resolution of electoral disputes.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
conscription law
A conscription law is a legal framework that mandates compulsory enlistment of individuals, typically citizens of a certain age group, into a nation's military or other forms of national service.
- 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_69ca842123588190b3f2e1a69037d141 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:34 p.m.