Triple
T14855521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etz Hayyim Synagogue |
E349339
|
entity |
| Predicate | wasRestored |
P13045
|
FINISHED |
| Object | after World War II |
—
|
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: after World War II | Statement: [Etz Hayyim Synagogue, wasRestored, after World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRestored Context triple: [Etz Hayyim Synagogue, wasRestored, after World War II]
-
A.
wasRestoredAt
Indicates that an entity was brought back to a previous or improved state at a specific time or place.
-
B.
restored
Indicates that an entity has returned another entity to a previous or improved state, condition, or position after damage, loss, or alteration.
-
C.
hasRestoration
chosen
Indicates that an entity has undergone, is undergoing, or is associated with a process of repair, renewal, or restoration.
-
D.
restoredBy
Indicates that an entity has been returned to a previous or improved state through the actions or intervention of another entity.
-
E.
temporarilyRestored
Indicates that a previously unavailable or altered state, condition, or connection has been brought back to its former status for a limited or non-permanent period.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded44458ec8190be295a95f5daab14 |
completed | April 14, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:54 a.m.