Triple

T32008765
Position Surface form Disambiguated ID Type / Status
Subject Roman Catholic Archdiocese of Lecce E817341 entity
Predicate governsCity P158171 FINISHED
Object Lecce 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: Lecce | Statement: [Roman Catholic Archdiocese of Lecce, governsCity, Lecce]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: governsCity
Context triple: [Roman Catholic Archdiocese of Lecce, governsCity, Lecce]
  • A. governsMajorCityIn
    Indicates that a governing entity has official administrative or political authority over a major city located within a specified region or jurisdiction.
  • B. capitalCityGoverningFrom
    Indicates that a specified capital city serves as the administrative center from which a given political entity is governed.
  • C. capitalCityGoverned chosen
    Indicates that a particular capital city is under the administrative or political authority of a specified governing body or jurisdiction.
  • D. nicknameOfCityItGoverns
    Indicates that one entity is a nickname used to refer to a city that another entity governs.
  • E. governsRegionWithLargestCity
    Indicates that a governing entity has authority over the region that contains the largest city in a specified area or jurisdiction.
  • 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_69f348f9e5d081908cc3f57c4942af52 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_6a002962f6e081909906d6436bae6407 completed May 10, 2026, 6:44 a.m.
PD Predicate disambiguation batch_6a00284c9c7c8190a77f18a41eee55df completed May 10, 2026, 6:40 a.m.
Created at: May 1, 2026, 12:15 a.m.