Triple
T20731167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Additional Act of 1834 |
E509574
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Brazilian legal document |
C43508
|
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: Brazilian legal document Context triple: [Additional Act of 1834, instanceOf, Brazilian legal document]
-
A.
Portuguese statute
A Portuguese statute is a formal written law enacted by the legislative authority of Portugal that establishes binding legal rules and obligations within its jurisdiction.
-
B.
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.
-
C.
Brazilian federal complementary law
A Brazilian federal complementary law is a special type of statute, approved by an absolute majority in the National Congress, that supplements and details constitutional provisions on matters expressly reserved by the Federal Constitution.
-
D.
Spanish legal instrument
A Spanish legal instrument is a formal document or act, recognized under Spanish law, that creates, modifies, transfers, or extinguishes legal rights and obligations.
-
E.
foundational document of Mercosur
A foundational document of Mercosur is a formal legal instrument, such as a treaty or protocol, that establishes, structures, or significantly governs the creation, principles, institutions, and functioning of the Southern Common Market (Mercosur).
- 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_69e0b4c589c08190834fb5d86d0efa2b |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:30 p.m.