Triple
T19173900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of Brazil |
E469392
|
entity |
| Predicate | prohibitsAmendmentOf |
P9570
|
FINISHED |
| Object | federative form of state |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: federative form of state | Statement: [Constitution of Brazil, prohibitsAmendmentOf, federative form of state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prohibitsAmendmentOf Context triple: [Constitution of Brazil, prohibitsAmendmentOf, federative form of state]
-
A.
cannotBeAmendedInRespectOf
chosen
Indicates that a particular item (such as a term, provision, or condition) is not allowed to be changed or modified in the specified respect or aspect.
-
B.
isAmendmentTo
Indicates that one item formally modifies, revises, or adds to the content or terms of another item.
-
C.
prohibits
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
-
D.
legalAmendment
Indicates a formal change or modification made to an existing law, regulation, or legal document.
-
E.
supportedAmendment
Indicates that one entity endorsed, backed, or voted in favor of a particular amendment.
- F. None of above.
Provenance (3 batches)
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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f16613dc8190987c2d79dc616e40 |
completed | April 20, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.