Triple
T26324451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Safad |
E662209
|
entity |
| Predicate | hasNotableSynagogue |
P84438
|
FINISHED |
| Object | Ari Ashkenazi 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: Ari Ashkenazi Synagogue | Statement: [Safad, hasNotableSynagogue, Ari Ashkenazi Synagogue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSynagogue Context triple: [Safad, hasNotableSynagogue, Ari Ashkenazi Synagogue]
-
A.
hasSynagogueType
Indicates the specific classification or type of synagogue associated with an entity.
-
B.
hasNotableReligiousCommunity
Indicates that an entity is known for having a significant or prominent religious community associated with it.
-
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.
mainSynagogue
chosen
Indicates that one entity serves as the primary or principal synagogue associated with another entity (such as a place, community, or organization).
-
E.
hasSynagogueUnion
Indicates that there exists an organizational or formal union connecting one synagogue with another synagogue or group of synagogues.
- 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: April 26, 2026, 10:30 p.m.