Triple

T23576239
Position Surface form Disambiguated ID Type / Status
Subject Monsey, New York E580263 entity
Predicate religiousInstitutionTypePresent P31566 FINISHED
Object synagogue 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: synagogue | Statement: [Monsey, New York, religiousInstitutionTypePresent, synagogue]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: religiousInstitutionTypePresent
Context triple: [Monsey, New York, religiousInstitutionTypePresent, synagogue]
  • A. hasReligiousInstitutionType chosen
    Indicates that an entity is associated with, or classified by, a specific type of religious institution.
  • B. religiousInstitutionLinked
    Indicates that there is an established connection or association between a religious institution and another entity.
  • C. religiousInstitutionShared
    Indicates that two entities are associated with or participate in the same religious institution or organization.
  • 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. religiousServiceType
    Indicates the specific kind or category of religious service associated with an event or context.
  • 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_69e24601a9108190bc31e83833c980e4 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f1afd6608481909a0d293ba8f65b2b completed April 29, 2026, 7:14 a.m.
PD Predicate disambiguation batch_69f118bcc0b08190b25a8dddfd461a0e completed April 28, 2026, 8:29 p.m.
Created at: April 17, 2026, 6:38 p.m.