Triple
T30685603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rivadavia Law of Ecclesiastical Reform |
E781176
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Argentine legal measure |
C54226
|
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: Argentine legal measure Context triple: [Rivadavia Law of Ecclesiastical Reform, instanceOf, Argentine legal measure]
-
A.
Argentine statute
chosen
An Argentine statute is a formal written law enacted by Argentina’s legislative authority that establishes binding legal rules and standards within the country’s jurisdiction.
-
B.
Argentine national law
Argentine national law is the body of legal norms, principles, and institutions that govern public and private relations within Argentina, established by its Constitution, legislation, regulations, and judicial decisions.
-
C.
Chilean legal instrument
A Chilean legal instrument is a formal, legally binding document or act—such as a law, decree, regulation, contract, or judicial decision—issued or recognized under Chilean law to create, modify, interpret, or extinguish rights and obligations.
-
D.
Uruguayan law
Uruguayan law is the legal system of the Oriental Republic of Uruguay, based on a civil law tradition derived from continental European codes, governing public, private, and constitutional matters within its territory.
-
E.
Spanish legal act
A Spanish legal act is a formal, binding provision or decision issued by a competent authority within Spain’s legal system that creates, modifies, or extinguishes rights and obligations under Spanish law.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:33 p.m.