Triple

T24013037
Position Surface form Disambiguated ID Type / Status
Subject Uruguay E594590 entity
Predicate recognizedAsCoPatronBy P154862 FINISHED
Object some Catholic devotional groups 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: some Catholic devotional groups | Statement: [Uruguay, recognizedAsCoPatronBy, some Catholic devotional groups]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: recognizedAsCoPatronBy
Context triple: [Uruguay, recognizedAsCoPatronBy, some Catholic devotional groups]
  • A. usedAsPatronOf
    Indicates that one entity serves as a patron or sponsor for another, providing support, endorsement, or backing.
  • B. recognizedAsRepresentativeBy
    Indicates that one entity is acknowledged or accepted by another entity as acting as its representative.
  • C. recognizedFor
    Indicates that one entity is acknowledged, credited, or honored for a particular achievement, quality, contribution, or work associated with another entity.
  • D. recognizedAs
    Indicates that one entity is acknowledged or accepted as having the identity, role, status, or classification of another entity.
  • E. areRecognizedBy
    Indicates that one entity acknowledges, identifies, or accepts another entity as valid, known, or legitimate.
  • 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_69e288bc8f608190ac4af29f0bd1c744 completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1d59ee0a08190ad1e1bc2dad1dda7 completed April 29, 2026, 9:55 a.m.
PD Predicate disambiguation batch_69f17639d23c8190bed93434e2f9230a completed April 29, 2026, 3:08 a.m.
PDg Predicate description generation batch_69f17c28b684819084eea522126463f8 completed April 29, 2026, 3:34 a.m.
Created at: April 17, 2026, 9:41 p.m.