Triple
T202343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hebron Patriarchs’ Cave |
E4531
|
entity |
| Predicate | hasReligiousComplex |
P916
|
FINISHED |
| Object | mosque |
—
|
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: mosque | Statement: [Hebron Patriarchs’ Cave, hasReligiousComplex, mosque]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousComplex Context triple: [Hebron Patriarchs’ Cave, hasReligiousComplex, mosque]
-
A.
hadViewOnReligion
Indicates that an entity held a particular perspective, belief, or stance regarding religion.
-
B.
hasReligiousSite
chosen
Indicates that a location or entity possesses, contains, or is associated with a religious site such as a temple, church, mosque, shrine, or similar place of worship.
-
C.
recognizesReligion
Indicates that one entity formally acknowledges or accepts another entity as a valid or legitimate religion.
-
D.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
E.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c2ead8481909996042efcae5e9d |
completed | Feb. 28, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69a25b4a0d448190a6fa6aeb30dc7e13 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.