Triple

T31225920
Position Surface form Disambiguated ID Type / Status
Subject Palais synodal de Sens E796135 entity
Predicate religiousJurisdictionLevel P16389 FINISHED
Object archiepiscopal see 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: archiepiscopal see | Statement: [Palais synodal de Sens, religiousJurisdictionLevel, archiepiscopal see]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: religiousJurisdictionLevel
Context triple: [Palais synodal de Sens, religiousJurisdictionLevel, archiepiscopal see]
  • A. religiousJurisdiction chosen
    Indicates that one entity holds official religious authority or governance over another entity or area.
  • B. laterReligiousJurisdiction
    Indicates that one entity subsequently became the religious authority or jurisdiction over another entity at a later time.
  • C. religiousCourtsJurisdiction
    Indicates that religious courts have legal authority or decision-making power over certain matters or individuals.
  • D. jurisdictionLevel
    Indicates the scope or tier of authority under which an entity or action is legally governed or regulated.
  • E. religiousLawView
    Indicates a person's stance, interpretation, or opinion regarding a particular religious law or set of religious legal principles.
  • 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_69f224da98f88190ab32f690cce5d303 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fe7b1c506c8190869c1a22031e0571 completed May 9, 2026, 12:09 a.m.
PD Predicate disambiguation batch_69fe796b2bdc8190a86980d44008f875 completed May 9, 2026, 12:01 a.m.
Created at: April 29, 2026, 9:10 p.m.