Triple

T33425392
Position Surface form Disambiguated ID Type / Status
Subject congresos de la CONMEBOL E855960 entity
Predicate puedenSerConvocadosPor P176597 FINISHED
Object Consejo de la CONMEBOL 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: Consejo de la CONMEBOL | Statement: [congresos de la CONMEBOL, puedenSerConvocadosPor, Consejo de la CONMEBOL]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: puedenSerConvocadosPor
Context triple: [congresos de la CONMEBOL, puedenSerConvocadosPor, Consejo de la CONMEBOL]
  • A. councilConvokedBy
    Indicates that a council or formal assembly was called together or convened by a particular person, group, or authority.
  • B. convenesOnRequestOf
    Indicates that one entity is brought together or assembled at the initiative or formal request of another entity.
  • C. convenedFor
    Indicates that an event, meeting, or gathering was brought together for a specific purpose, topic, or beneficiary.
  • D. canBeRecruitedFrom
    Indicates that one entity is eligible to be recruited, obtained, or enlisted starting from or via another specified entity or source.
  • E. convenesFrom
    Indicates that an event, meeting, or gathering is initiated or brought together starting from a specified source, time, or context.
  • 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_69f3496fdf0081908c1aa30870ce518b completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6e52a6d40819084472f6072c91e9f completed May 3, 2026, 6:03 a.m.
PD Predicate disambiguation batch_69f6e3da41948190a4cfe866ce184f73 completed May 3, 2026, 5:57 a.m.
PDg Predicate description generation batch_69f6e47c13348190a10528c84a401178 completed May 3, 2026, 6 a.m.
Created at: May 1, 2026, 1:36 a.m.