Triple

T19313792
Position Surface form Disambiguated ID Type / Status
Subject Gandersheim E483040 entity
Predicate wasReligiousCenterIn P23109 FINISHED
Object early Holy Roman Empire 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: early Holy Roman Empire | Statement: [Gandersheim, wasReligiousCenterIn, early Holy Roman Empire]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasReligiousCenterIn
Context triple: [Gandersheim, wasReligiousCenterIn, early Holy Roman Empire]
  • A. tookPlaceAtReligiousCenter
    Indicates that an event or action occurred at a religious center or place of worship.
  • B. hasReligiousHeadquarters
    Indicates that an organization or religious group has its main religious administrative center or headquarters located at a specific place.
  • C. ecclesiasticalCenter chosen
    Indicates that a place functions as a primary religious or church administrative hub for a surrounding area or community.
  • D. isMajorReligiousInstitutionIn
    Indicates that a major religious institution (such as a church, mosque, temple, or similar body) is located within or primarily based in a specified place or region.
  • E. isPlaceOfPilgrimageFor
    Indicates that a location serves as a destination for religious or spiritual pilgrimage for a person or group.
  • 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_69d8e8d04d5c8190baa816986f2b1d1e completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e604cfec8c8190a118b327b1418150 completed April 20, 2026, 10:49 a.m.
PD Predicate disambiguation batch_69e4dd0ef66881909d489d634eee817a completed April 19, 2026, 1:47 p.m.
Created at: April 10, 2026, 1:32 p.m.