Triple
T30637106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohel Moshe Synagogue |
E779868
|
entity |
| Predicate | eraOfRefugeeUse |
P74118
|
FINISHED |
| Object | late 1930s |
—
|
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: late 1930s | Statement: [Ohel Moshe Synagogue, eraOfRefugeeUse, late 1930s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfRefugeeUse Context triple: [Ohel Moshe Synagogue, eraOfRefugeeUse, late 1930s]
-
A.
wasRefugee
Indicates that an entity previously lived as a refugee, having been forced to leave their home country due to conflict, persecution, or disaster.
-
B.
designatedAsRefuge
chosen
Indicates that an entity has been officially assigned or recognized as a refuge or place of protection.
-
C.
grantedRefugeTo
Indicates that one entity provided shelter, protection, or safe haven to another entity, typically in a context of danger, persecution, or displacement.
-
D.
refugeeAdministration
Indicates the management, coordination, or oversight of services, policies, and procedures related to refugees.
-
E.
takenAsRefugeBy
Indicates that one entity is used or relied upon by another entity as a place or source of safety, protection, or refuge.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 29, 2026, 8:28 p.m.