Triple

T31042826
Position Surface form Disambiguated ID Type / Status
Subject Diocese of Worms E791041 entity
Predicate wasImperialEstate P45988 FINISHED
Object yes 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: yes | Statement: [Diocese of Worms, wasImperialEstate, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasImperialEstate
Context triple: [Diocese of Worms, wasImperialEstate, yes]
  • A. establishedAsImperialEstate
    Indicates that something has been formally designated or set up as an imperial estate under the authority of an empire.
  • B. heldImperialEstate chosen
    Indicates that an entity possessed or controlled land or property classified as an imperial estate under a particular imperial authority.
  • C. servedAsImperialResidenceFrom
    Indicates that an entity functioned as an imperial residence starting from a specified point in time.
  • D. hasImperialPalace
    Indicates that an entity possesses or is the location of an official imperial palace.
  • E. hadEstates
    Indicates that an entity possessed or owned one or more estates (properties or landholdings).
  • 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_69f224ca2fa881908a3ac5fedf207b90 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f697eabb048190bc01a830f14942c6 completed May 3, 2026, 12:33 a.m.
PD Predicate disambiguation batch_69f69664142c8190bc695501056b0236 completed May 3, 2026, 12:27 a.m.
Created at: April 29, 2026, 8:59 p.m.