Triple
T29261327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ofakim |
E741852
|
entity |
| Predicate | hasReligiousInfrastructure |
P916
|
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: [Ofakim, hasReligiousInfrastructure, synagogues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousInfrastructure Context triple: [Ofakim, hasReligiousInfrastructure, synagogues]
-
A.
hasReligiousBuildingAlong
Indicates that a religious building is located along the course, path, or extent of the referenced entity.
-
B.
hasReligiousSite
chosen
Indicates that a location or entity possesses, contains, or is associated with a religious site such as a temple, church, mosque, shrine, or similar place of worship.
-
C.
hasReligiousStructureType
Indicates that a religious structure is classified as being of a specific type or category of religious building.
-
D.
inReligiousStructure
Indicates that one entity is located within or inside a building or structure used for religious purposes.
-
E.
hasClericalStructure
Indicates that an entity possesses an organized clerical or administrative hierarchy or framework.
- 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69ffdf47d9608190830ca23d9cef6409 |
completed | May 10, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69ffdf00e2b4819082dd5cb78f316baf |
completed | May 10, 2026, 1:27 a.m. |
Created at: April 28, 2026, 12:41 p.m.