Triple
T2637827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yokneam Illit |
E59789
|
entity |
| Predicate | hasReligiousFacilityType |
P34373
|
FINISHED |
| Object | synagogues |
—
|
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: synagogues | Statement: [Yokneam Illit, hasReligiousFacilityType, synagogues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousFacilityType Context triple: [Yokneam Illit, hasReligiousFacilityType, synagogues]
-
A.
hasReligiousInstitutionType
Indicates that an entity is associated with, or classified by, a specific type of religious institution.
-
B.
hasFacilityType
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
C.
religiousSiteType
chosen
Indicates the specific kind or category of religious site associated with an entity (e.g., church, mosque, temple).
-
D.
isPlaceOfWorshipFor
Indicates that a location serves as a site where members of a particular religion or belief system perform worship or religious practices.
-
E.
hasPlaceOfWorship
Indicates that an entity possesses, contains, or is associated with a designated location used for religious or spiritual worship.
- 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_69ab4ac8596c8190b34997e73d9e991c |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd8e470ac8190bd0d6de6805afcd0 |
completed | March 7, 2026, 7:51 a.m. |
| PD | Predicate disambiguation | batch_69abd812849881908f956845a80e0205 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.