Triple
T5639897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurva Synagogue (unbuilt project) |
E124238
|
entity |
| Predicate | reasonNotBuilt |
P57902
|
FINISHED |
| Object | political considerations |
—
|
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: political considerations | Statement: [Hurva Synagogue (unbuilt project), reasonNotBuilt, political considerations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonNotBuilt Context triple: [Hurva Synagogue (unbuilt project), reasonNotBuilt, political considerations]
-
A.
builtWithout
Indicates that something was constructed or created in the absence of a particular component, material, tool, or condition.
-
B.
reasonForNoProduction
Indicates the specific cause or explanation for why production did not occur.
-
C.
notRebuiltAfter
Indicates that an entity was destroyed or damaged and has not been reconstructed or restored after a specified event or point in time.
-
D.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
-
E.
reasonForNotCompletion
chosen
Indicates the explanation or cause for why a task, process, or obligation was not completed.
- 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022850bf08190953cd5394f821801 |
completed | March 22, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.