Triple

T29888228
Position Surface form Disambiguated ID Type / Status
Subject Lei nº 11.516, de 28 de agosto de 2007 E759073 entity
Predicate dataDeSanção P168214 FINISHED
Object 28 de agosto de 2007 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: 28 de agosto de 2007 | Statement: [Lei nº 11.516, de 28 de agosto de 2007, dataDeSanção, 28 de agosto de 2007]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: dataDeSanção
Context triple: [Lei nº 11.516, de 28 de agosto de 2007, dataDeSanção, 28 de agosto de 2007]
  • A. coSanctions
    Indicates that two or more entities jointly impose or support the same sanction or set of sanctions on a target.
  • B. coSanctionedBy
    Indicates that an action, decision, or measure is jointly authorized, approved, or endorsed by multiple entities.
  • C. coSanctionsWith
    Indicates that two or more entities jointly impose, support, or participate in the same sanctions or sanctioning action.
  • D. coSanctionedWith
    Indicates that an entity is subject to sanctions together with another entity, typically as part of the same sanctioning action or regime.
  • E. isSanctionedBy
    Indicates that an entity is subject to official penalties, restrictions, or punitive measures imposed by another authority or organization.
  • F. None of above. chosen

Provenance (4 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.
PDg Predicate description generation batch_69f67256d064819094be04fc1bbbc635 completed May 2, 2026, 9:53 p.m.
Created at: April 29, 2026, 6:01 p.m.