Triple

T32045183
Position Surface form Disambiguated ID Type / Status
Subject Beachwood E818325 entity
Predicate hasJewishCommunityPresence P126115 FINISHED
Object true 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: true | Statement: [Beachwood, hasJewishCommunityPresence, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasJewishCommunityPresence
Context triple: [Beachwood, hasJewishCommunityPresence, true]
  • A. hasSignificantJewishCommunity chosen
    Indicates that a place or entity possesses a notably large, influential, or historically important Jewish community.
  • B. hasJewishCommunityHistory
    Indicates that there is a documented history of a Jewish community being present, active, or influential in relation to the subject.
  • C. hasJewishCommunityUntil
    Indicates that a place had an established Jewish community that existed there up to a certain end date or period.
  • D. hasJewishInstitution
    Indicates that a place, organization, or entity possesses, hosts, or is associated with a Jewish religious, cultural, or educational institution.
  • E. hasSynagogueHistory
    Indicates that there exists a historical relationship or record connecting an entity to a synagogue, such as past ownership, use, events, or significance.
  • 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_69f348fcfb648190859f6be5e04b7cfe completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6b4c1328081909758375193b2ccf7 completed May 3, 2026, 2:36 a.m.
PD Predicate disambiguation batch_69f6b154b3dc819087115f5f63f7b00f completed May 3, 2026, 2:22 a.m.
Created at: May 1, 2026, 12:20 a.m.