Triple
T5639875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurva Synagogue (unbuilt project) |
E124238
|
entity |
| Predicate | materialConcept |
P65357
|
FINISHED |
| Object | massive stone walls |
—
|
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: massive stone walls | Statement: [Hurva Synagogue (unbuilt project), materialConcept, massive stone walls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: materialConcept Context triple: [Hurva Synagogue (unbuilt project), materialConcept, massive stone walls]
-
A.
material
Indicates that one entity is physically composed of, made from, or constructed using the substance or material represented by the other entity.
-
B.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
C.
materialDepicted
Indicates that a work or representation visually portrays or includes a particular material as part of its subject.
-
D.
materialDescribedAs
Indicates that a material is characterized or specified using a particular descriptive term, label, or textual description.
-
E.
featuresMaterialFrom
Indicates that one entity incorporates, contains, or is composed of material originating from another entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69c01f0727bc8190b16e9a669c04b4dd |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:41 p.m.