Triple
T29888241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lei nº 11.516, de 28 de agosto de 2007 |
E759073
|
entity |
| Predicate | tipoDeAtoNormativo |
P2588
|
FINISHED |
| Object | lei ordinária |
—
|
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: lei ordinária | Statement: [Lei nº 11.516, de 28 de agosto de 2007, tipoDeAtoNormativo, lei ordinária]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tipoDeAtoNormativo Context triple: [Lei nº 11.516, de 28 de agosto de 2007, tipoDeAtoNormativo, lei ordinária]
-
A.
typeOfLegislation
chosen
Indicates the specific category or kind of legislation that a given legal act or measure belongs to.
-
B.
regulatoryType
Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
-
C.
legalStandardType
Indicates the specific type or category of legal standard that governs or applies to a given legal rule, decision, or evaluation.
-
D.
legalCodeType
Indicates the specific category or classification of a legal code that applies to an entity or situation.
-
E.
normativeFor
Indicates that something establishes, prescribes, or encodes the norms, standards, or rules that should govern another thing’s behavior or state.
- 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_69f2245de2f48190a481404896b56254 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f676fe75988190ae1bffb155a3c4e1 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:01 p.m.