Triple

T354148
Position Surface form Disambiguated ID Type / Status
Subject Diocese of Honduras E7506 entity
Predicate governingStructure P220 FINISHED
Object episcopal polity 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: episcopal polity | Statement: [Diocese of Honduras, governingStructure, episcopal polity]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: governingStructure
Context triple: [Diocese of Honduras, governingStructure, episcopal polity]
  • A. governingBodyLevel
    Indicates the hierarchical level or tier at which a governing body operates within a political or organizational structure.
  • B. governmentType chosen
    Indicates the form or system of governance under which an entity (such as a country or organization) is organized and ruled.
  • C. hasGovernmentBody
    Indicates that one entity serves as the official governing or administrative body responsible for overseeing or managing another entity.
  • D. formedGovernmentIn
    Indicates that an entity established or took office as the governing authority of a political unit in a specified place or jurisdiction.
  • E. hasMainGoverningBody
    Indicates that an entity possesses a primary official organization or authority responsible for its overall governance or decision-making.
  • 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_69a2e7e696948190bebc966535995e45 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2eb8312f4819084dc222e665fded3 completed Feb. 28, 2026, 1:20 p.m.
PD Predicate disambiguation batch_69a2e9571bd88190b6fcb16f21604720 completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.