Triple

T18654878
Position Surface form Disambiguated ID Type / Status
Subject Roman Catholic Diocese of Soissons E456032 entity
Predicate cathedralType P9020 FINISHED
Object cathedral church 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: cathedral church | Statement: [Roman Catholic Diocese of Soissons, cathedralType, cathedral church]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: cathedralType
Context triple: [Roman Catholic Diocese of Soissons, cathedralType, cathedral church]
  • A. cathedralChurch
    Indicates that one church serves as the cathedral (principal church and episcopal seat) of another ecclesiastical jurisdiction or entity.
  • B. cathedral chosen
    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.
  • C. hasCathedralType
    Indicates that an entity is associated with, classified by, or designated as having a specific type or category of cathedral.
  • D. cathedralFeature
    Indicates that one entity is a distinctive architectural or structural feature of a cathedral.
  • E. coCathedral
    Indicates that a church shares the status and functions of a cathedral with another cathedral within the same diocese or ecclesiastical 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_69d8d38ea1e88190997e9b231190ba6f completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e55084012881909b9dd60565011c86 completed April 19, 2026, 10 p.m.
PD Predicate disambiguation batch_69e478d85864819093cbad5ed9b54878 completed April 19, 2026, 6:40 a.m.
Created at: April 10, 2026, 11:47 a.m.