Triple
T31474312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law on the Special Legal Status of Gagauzia |
E802949
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Moldovan statute |
C46851
|
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: Moldovan statute Context triple: [Law on the Special Legal Status of Gagauzia, instanceOf, Moldovan statute]
-
A.
Moldovan law
chosen
Moldovan law is the body of legal norms, principles, and institutions governing the Republic of Moldova, shaped by its civil law tradition, constitutional framework, and evolving European integration commitments.
-
B.
Romanian law
Romanian law is the national legal system of Romania, based primarily on civil law traditions, that regulates the rights, obligations, and interactions of individuals, organizations, and public authorities within the Romanian state.
-
C.
district of Moldova
A district of Moldova is an administrative territorial unit within the country, typically comprising multiple towns and villages and governed by a local public authority responsible for regional administration and services.
-
D.
Belarusian law
Belarusian law is the system of legal norms and institutions governing social relations in Belarus, shaped by its constitution, legislation, presidential decrees, and influences from both Soviet legal traditions and contemporary international law.
-
E.
Ukrainian legislation
Ukrainian legislation is the system of legal norms, acts, and regulations adopted by competent Ukrainian authorities that govern social relations, define rights and obligations, and establish the legal framework of the state.
- 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_69f348c9477c8190bc0a21f6d482d2fc |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:28 p.m.