Triple

T10566036
Position Surface form Disambiguated ID Type / Status
Subject Archdiocese of Turin E249351 entity
Predicate usesCathedralFor P94692 FINISHED
Object major diocesan liturgies 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: major diocesan liturgies | Statement: [Archdiocese of Turin, usesCathedralFor, major diocesan liturgies]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesCathedralFor
Context triple: [Archdiocese of Turin, usesCathedralFor, major diocesan liturgies]
  • A. cathedralChurch
    Indicates that one church serves as the cathedral (principal church and episcopal seat) of another ecclesiastical jurisdiction or entity.
  • B. containsCathedral
    Indicates that one entity includes or has within its boundaries a cathedral associated with it.
  • 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. coCathedral
    Indicates that a church shares the status and functions of a cathedral with another cathedral within the same diocese or ecclesiastical jurisdiction.
  • E. usesCathedralAsSee
    Indicates that a religious jurisdiction or authority has a particular cathedral as the location of its episcopal seat (its see).
  • 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_69d381c8bd708190acf3d275c908251e completed April 6, 2026, 9:50 a.m.
NER Named-entity recognition batch_69d5272ce78c8190bf3227053ef88a48 completed April 7, 2026, 3:47 p.m.
PD Predicate disambiguation batch_69d51901ff6c819095e7b528170a69dc completed April 7, 2026, 2:47 p.m.
PDg Predicate description generation batch_69d5270eca0481908573b698390c5b08 completed April 7, 2026, 3:47 p.m.
Created at: April 6, 2026, 12:36 p.m.