Triple

T13915326
Position Surface form Disambiguated ID Type / Status
Subject Bishop of Pavia E334605 entity
Predicate traditionallyResidesIn P112276 FINISHED
Object episcopal residence of Pavia 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: episcopal residence of Pavia | Statement: [Bishop of Pavia, traditionallyResidesIn, episcopal residence of Pavia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: traditionallyResidesIn
Context triple: [Bishop of Pavia, traditionallyResidesIn, episcopal residence of Pavia]
  • A. locatedInTraditionalRegion
    Indicates that an entity is situated within a specific traditional or historically recognized region.
  • B. traditionalRegionOfResidence
    Indicates the customary or historically established geographic region where an entity (typically a person or group) resides or is considered to be from.
  • C. hasTraditionalResidenceCountry
    Indicates that an entity’s customary or long-term country of residence is the specified country.
  • D. hasResidenceIn
    Indicates that an entity lives or maintains a primary dwelling in a specified location.
  • E. traditionallyFoundIn
    Indicates that something is customarily or historically located, used, or present within a particular place, context, or setting.
  • 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_69d81c5eaa9c819083b1ff8689179565 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de27260ae08190be45b4b15898e365 completed April 14, 2026, 11:38 a.m.
PD Predicate disambiguation batch_69de059e4ba881908554f72e889719fa completed April 14, 2026, 9:15 a.m.
PDg Predicate description generation batch_69de239524688190a0f2408c239cfcaa completed April 14, 2026, 11:23 a.m.
Created at: April 9, 2026, 10:16 p.m.