Triple

T19493018
Position Surface form Disambiguated ID Type / Status
Subject Archdiocese of Freiburg E487698 entity
Predicate usesCathedralAs P79002 FINISHED
Object seat of the archbishop 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: seat of the archbishop | Statement: [Archdiocese of Freiburg, usesCathedralAs, seat of the archbishop]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesCathedralAs
Context triple: [Archdiocese of Freiburg, usesCathedralAs, seat of the archbishop]
  • A. usesCathedralFor
    Indicates that an entity employs or makes use of a cathedral for a particular purpose or activity.
  • B. cathedralChurch
    Indicates that one church serves as the cathedral (principal church and episcopal seat) of another ecclesiastical jurisdiction or entity.
  • C. usesCathedralAsSee chosen
    Indicates that a religious jurisdiction or authority has a particular cathedral as the location of its episcopal seat (its see).
  • D. cathedralSince
    Indicates that an entity has held the status or function of a cathedral continuously from a specified point in time onward.
  • E. 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.
  • 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_69d8e8d9d1c88190b01cd78b8be49384 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6348f4d708190a6e612863fee4b97 completed April 20, 2026, 2:13 p.m.
PD Predicate disambiguation batch_69e4fd7883308190b73912a71a35a835 completed April 19, 2026, 4:06 p.m.
Created at: April 10, 2026, 1:39 p.m.