Triple

T31017010
Position Surface form Disambiguated ID Type / Status
Subject Worms E790349 entity
Predicate hasJewishCommunitySince P91263 FINISHED
Object Middle Ages 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: Middle Ages | Statement: [Worms, hasJewishCommunitySince, Middle Ages]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasJewishCommunitySince
Context triple: [Worms, hasJewishCommunitySince, Middle Ages]
  • A. hasJewishCommunityHistory chosen
    Indicates that there is a documented history of a Jewish community being present, active, or influential in relation to the subject.
  • B. hasJewishCommunityUntil
    Indicates that a place had an established Jewish community that existed there up to a certain end date or period.
  • C. hasSignificantJewishCommunity
    Indicates that a place or entity possesses a notably large, influential, or historically important Jewish community.
  • D. hasSynagogueHistory
    Indicates that there exists a historical relationship or record connecting an entity to a synagogue, such as past ownership, use, events, or significance.
  • E. hadSignificantJewishPopulationBeforeWorldWarII
    Indicates that the subject place or region had a notably large or influential Jewish community prior to the outbreak of World War II.
  • 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_69f224c811508190a7de096a5b1f5798 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f6953bafb88190a860e9c68a3dd4b2 completed May 3, 2026, 12:22 a.m.
PD Predicate disambiguation batch_69f690ef92308190903a54fc74233269 completed May 3, 2026, 12:03 a.m.
Created at: April 29, 2026, 8:58 p.m.