Triple

T26492595
Position Surface form Disambiguated ID Type / Status
Subject Roman Catholic Diocese of Lescar E669196 entity
Predicate historicCathedral P22831 FINISHED
Object Lescar Cathedral 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: Lescar Cathedral | Statement: [Roman Catholic Diocese of Lescar, historicCathedral, Lescar Cathedral]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicCathedral
Context triple: [Roman Catholic Diocese of Lescar, historicCathedral, Lescar Cathedral]
  • A. cathedralChurch
    Indicates that one church serves as the cathedral (principal church and episcopal seat) of another ecclesiastical jurisdiction or entity.
  • B. formerCathedral chosen
    Indicates that a building once held the status and function of a cathedral but no longer does.
  • C. cathedral
    Indicates that an entity is a cathedral, i.e., it has the status or function of a principal church, typically one that is the seat of a bishop.
  • D. cathedralSince
    Indicates that an entity has held the status or function of a cathedral continuously from a specified point in time onward.
  • E. hasHistoricCathedralCity
    Indicates that one entity is historically recognized as a cathedral city associated with or belonging to another entity.
  • 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_69eeb319007081909642b414b114b35a completed April 27, 2026, 12:51 a.m.
NER Named-entity recognition batch_69f9fd6834cc8190aa27153d6a99f3bb completed May 5, 2026, 2:23 p.m.
PD Predicate disambiguation batch_69f7cf769338819092a5f42653dcc956 completed May 3, 2026, 10:43 p.m.
Created at: April 27, 2026, 1:05 a.m.