Triple
T12208596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hittin |
E290897
|
entity |
| Predicate | holySiteFor |
P57618
|
FINISHED |
| Object | Druze community |
—
|
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: Druze community | Statement: [Hittin, holySiteFor, Druze community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holySiteFor Context triple: [Hittin, holySiteFor, Druze community]
-
A.
isPlaceOfPilgrimageFor
chosen
Indicates that a location serves as a destination for religious or spiritual pilgrimage for a person or group.
-
B.
holyCityFor
Indicates that a city holds recognized religious significance or sacred status for a particular religion or religious community.
-
C.
isPlaceOfWorshipFor
Indicates that a location serves as a site where members of a particular religion or belief system perform worship or religious practices.
-
D.
isPilgrimageDestination
Indicates that a place serves as a destination specifically visited by people undertaking a religious or spiritual pilgrimage.
-
E.
hasReligiousSite
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.
- 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d920e312708190b4aede2e21f5f697 |
completed | April 10, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69d91c3d669c81908eea7ad61122d275 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.