Triple
T37264806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law on the Organization of the National Defence System and Military Service of Lithuania |
E924353
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lithuanian statute |
C60717
|
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: Lithuanian statute Context triple: [Law on the Organization of the National Defence System and Military Service of Lithuania, instanceOf, Lithuanian statute]
-
A.
Lithuanian law
chosen
Lithuanian law is the national legal system of Lithuania, based on a civil law tradition and governed by the Constitution, statutes, and subordinate legislation regulating public, private, and administrative relations within the state.
-
B.
Latvian law
Latvian law is the national legal system of the Republic of Latvia, based on a civil law tradition and governed by its Constitution, statutes, regulations, and judicial practice.
-
C.
Slovak statute
A Slovak statute is a formal written law enacted by the National Council of the Slovak Republic that regulates specific areas of public or private life within Slovakia’s legal system.
-
D.
Lithuanian historical document
A Lithuanian historical document is an original or reproduced written, printed, or otherwise recorded source created in or about Lithuania’s past, providing evidence of historical events, governance, culture, or social life.
-
E.
Czech statute
A Czech statute is a formal written law enacted by the Parliament of the Czech Republic that establishes, modifies, or regulates legal rights and obligations within the Czech legal system.
- 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:15 p.m.