Triple
T26324434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Safad |
E662209
|
entity |
| Predicate | otherHolyCitiesOfJudaism |
P6452
|
FINISHED |
| Object | Jerusalem |
—
|
NE NERFINISHED |
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 | Statement: [Safad, otherHolyCitiesOfJudaism, Jerusalem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: otherHolyCitiesOfJudaism Context triple: [Safad, otherHolyCitiesOfJudaism, Jerusalem]
-
A.
holyCityFor
chosen
Indicates that a city holds recognized religious significance or sacred status for a particular religion or religious community.
-
B.
regionOfReligiousSignificance
Indicates that a location or area holds recognized religious importance, such as being sacred, holy, or central to religious practices or beliefs.
-
C.
holiestSiteIn
Indicates that a site is considered the most sacred or religiously significant location within a particular place or region.
-
D.
cityOnWestBank
Indicates that a city is located on the western bank of a river or other significant body of water.
-
E.
biblicalCityName
Indicates that the entity is identified by a name used for a city in the Bible.
- 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 26, 2026, 10:30 p.m.