Triple

T22480727
Position Surface form Disambiguated ID Type / Status
Subject Rowno E555755 entity
Predicate hasReligiousCommunityHistorically P91263 FINISHED
Object Jewish 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: Jewish | Statement: [Rowno, hasReligiousCommunityHistorically, Jewish]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasReligiousCommunityHistorically
Context triple: [Rowno, hasReligiousCommunityHistorically, Jewish]
  • 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. religiousBackgroundOfCommunity
    Indicates the religious tradition, affiliation, or belief system that characterizes or predominates within a particular community.
  • C. hasChristianCommunity
    Indicates that a place or entity possesses or hosts an established Christian community.
  • D. religionHistoricallyAssociated
    Indicates a historical association between an entity and a particular religion, based on past practice, tradition, or cultural linkage rather than current or official status.
  • E. hasReligiousMovement
    Indicates that an entity is associated with, follows, or is characterized by a particular religious movement.
  • 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_69e11e53897c819088863779f8c50bb0 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15c3836a08190b6f0d88b94cb80a3 completed April 29, 2026, 1:17 a.m.
PD Predicate disambiguation batch_69e898b6eee08190ba673a0ee329e671 completed April 22, 2026, 9:45 a.m.
Created at: April 16, 2026, 8:49 p.m.