Triple

T31633909
Position Surface form Disambiguated ID Type / Status
Subject Portuguese Jewish community of Amsterdam E807244 entity
Predicate hasMainSynagogue P84438 FINISHED
Object Portuguese Synagogue NE NERFINISHED

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: Portuguese Synagogue | Statement: [Portuguese Jewish community of Amsterdam, hasMainSynagogue, Portuguese Synagogue]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMainSynagogue
Context triple: [Portuguese Jewish community of Amsterdam, hasMainSynagogue, Portuguese Synagogue]
  • A. mainSynagogue chosen
    Indicates that one entity serves as the primary or principal synagogue associated with another entity (such as a place, community, or organization).
  • B. hasSynagogueType
    Indicates the specific classification or type of synagogue associated with an entity.
  • C. hasSynagogueHistory
    Indicates that there exists a historical relationship or record connecting an entity to a synagogue, such as past ownership, use, events, or significance.
  • D. hasSynagogueUnion
    Indicates that there exists an organizational or formal union connecting one synagogue with another synagogue or group of synagogues.
  • E. synagogueName
    Indicates that one entity is the name or designated title of a synagogue associated with another entity.
  • 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_69f348d892948190915f8facacb9568c completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_6a00332eaa0c8190a69ea895576bb0ee completed May 10, 2026, 7:26 a.m.
PD Predicate disambiguation batch_6a0032b2ea80819083b89ebb88165933 completed May 10, 2026, 7:24 a.m.
Created at: April 30, 2026, 10:46 p.m.