Triple

T29717025
Position Surface form Disambiguated ID Type / Status
Subject Cámara de Senadores E751939 entity
Predicate controla P4700 FINISHED
Object Poder Ejecutivo de Uruguay NE NERFINISHED

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 Ejecutivo de Uruguay | Statement: [Cámara de Senadores, controla, Poder Ejecutivo de Uruguay]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: controla
Context triple: [Cámara de Senadores, controla, Poder Ejecutivo de Uruguay]
  • A. controlsWith
    Indicates that one entity exercises authority, direction, or regulatory power over another entity through specific means or mechanisms.
  • B. controlled chosen
    Indicates that one entity has power, authority, or influence to direct, regulate, or determine the behavior, actions, or state of another entity.
  • C. centralizesControlOf
    Indicates that one entity consolidates and concentrates decision-making authority or governance power over another entity or set of entities.
  • D. exportControl
    Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
  • E. controlStand
    Indicates that one entity manages, directs, or regulates the operation or behavior of another entity or system.
  • 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_69f0d628c00c8190ab5ee7e423d7ec3c completed April 28, 2026, 3:45 p.m.
NER Named-entity recognition batch_69fd35d108908190b79b1e8e6bbd62aa completed May 8, 2026, 1:01 a.m.
PD Predicate disambiguation batch_69fd34cb46108190b43c3b7f67ec4cd4 completed May 8, 2026, 12:56 a.m.
Created at: April 28, 2026, 7:34 p.m.