Triple

T4297220
Position Surface form Disambiguated ID Type / Status
Subject Siscia E99742 entity
Predicate wasEpiscopalSee P2276 FINISHED
Object late Roman period 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: late Roman period | Statement: [Siscia, wasEpiscopalSee, late Roman period]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasEpiscopalSee
Context triple: [Siscia, wasEpiscopalSee, late Roman period]
  • A. episcopalSeeOf chosen
    Indicates that one entity serves as the episcopal see (the official seat or jurisdictional center) of a bishop or similar ecclesiastical authority for another entity.
  • B. majorArchepiscopalSee
    Indicates that one entity serves as the principal episcopal jurisdiction (major archiepiscopal see) governing or presiding over the other within a particular church or rite.
  • C. isDiocesanSeatOf
    Indicates that a location serves as the central administrative seat or headquarters of a particular diocese.
  • D. otherHistoricArchiepiscopalSee
    Indicates that an entity has or is associated with another historic archiepiscopal see distinct from its primary one.
  • E. episcopalSeeTransferredFrom
    Indicates that the location or jurisdiction of a bishop’s episcopal see has been moved from one place or authority to another.
  • 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_69b3455175088190aa79c6e03b86647e completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b3509aebd48190af38f2e37f07869a completed March 12, 2026, 11:47 p.m.
PD Predicate disambiguation batch_69b347fe55a88190b77bab0c0f38e1aa completed March 12, 2026, 11:10 p.m.
Created at: March 12, 2026, 11:08 p.m.