Triple

T30520227
Position Surface form Disambiguated ID Type / Status
Subject Bishopric of Durostorum E776673 entity
Predicate modernLocationOfSee P155515 FINISHED
Object Silistra, Bulgaria NE NERFINISHED

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: Silistra, Bulgaria | Statement: [Bishopric of Durostorum, modernLocationOfSee, Silistra, Bulgaria]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: modernLocationOfSee
Context triple: [Bishopric of Durostorum, modernLocationOfSee, Silistra, Bulgaria]
  • A. locationOfSee
    Indicates a relationship where a particular place is the setting or site in which an act of seeing or visual perception occurs.
  • B. modernLocationOfCity chosen
    Indicates that a historical or former city is located within the boundaries of a specified modern administrative or geographic entity.
  • C. historicalLocationOf
    Indicates that a place served as a significant site or setting for an entity during a particular historical period or event.
  • D. locatedInOrNearModernSettlement
    Indicates that something is situated within or in close proximity to a present-day town, city, or other populated settlement.
  • E. historicallyLocatedNear
    Indicates that, in a historical context, one entity was geographically situated close to another entity.
  • 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_69f2249b23c4819087fa85496d92f43f completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f78c61ed4c8190ad84c918fa9af55a completed May 3, 2026, 5:56 p.m.
PD Predicate disambiguation batch_69f78b8cb3a881909ebaac1b503988c2 completed May 3, 2026, 5:53 p.m.
Created at: April 29, 2026, 8:17 p.m.