Triple
T17221423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mamilla neighborhood |
E417991
|
entity |
| Predicate | buildingMaterialRequirement |
P112810
|
FINISHED |
| Object | Jerusalem stone cladding |
—
|
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: Jerusalem stone cladding | Statement: [Mamilla neighborhood, buildingMaterialRequirement, Jerusalem stone cladding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingMaterialRequirement Context triple: [Mamilla neighborhood, buildingMaterialRequirement, Jerusalem stone cladding]
-
A.
hasBuildingMaterialInHut
Indicates that a hut is constructed using a specified building material.
-
B.
productionRequirement
Indicates a condition or resource that must be fulfilled or available for a production process or activity to take place.
-
C.
buildingCondition
Indicates the physical state or quality of a building, such as how well it is preserved, maintained, or structurally sound.
-
D.
مادة البناء
chosen
Indicates a relationship where something serves as, or is used as, a construction material in building or structural work.
-
E.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dde78f881908b03105fa0298ae2 |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.