Triple
T29888249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lei nº 11.516, de 28 de agosto de 2007 |
E759073
|
entity |
| Predicate | poder |
P146019
|
FINISHED |
| Object | Poder Legislativo |
—
|
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: Poder Legislativo | Statement: [Lei nº 11.516, de 28 de agosto de 2007, poder, Poder Legislativo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: poder Context triple: [Lei nº 11.516, de 28 de agosto de 2007, poder, Poder Legislativo]
-
A.
powers
Indicates that one entity supplies or provides the energy, authority, or driving force that enables another entity to function or operate.
-
B.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
-
C.
esParteDePoder
chosen
Indicates that something is a component or constituent element of a larger power or authority structure.
-
D.
powerPosition
Indicates that one entity holds a position of authority, control, or dominance over another within a hierarchy or power structure.
-
E.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
- 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.