Triple
T3714118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Bireh |
E81483
|
entity |
| Predicate | hasReligiousBuildings |
P1191
|
FINISHED |
| Object | mosques |
—
|
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: mosques | Statement: [al-Bireh, hasReligiousBuildings, mosques]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousBuildings Context triple: [al-Bireh, hasReligiousBuildings, mosques]
-
A.
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.
-
B.
hasClericalStructure
Indicates that an entity possesses an organized clerical or administrative hierarchy or framework.
-
C.
religiousBuildingDesigned
Indicates that one entity (typically an architect or designer) is responsible for designing a religious building associated with the other entity.
-
D.
hasPlaceOfWorship
chosen
Indicates that an entity possesses, contains, or is associated with a designated location used for religious or spiritual worship.
-
E.
hasMosque
Indicates that one entity possesses, contains, or is the location of a mosque.
- 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_69ad8b1a81588190b3f27a5483bb610e |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adc9ccfad081908730ed15c6f87ce2 |
completed | March 8, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69adc041a8608190a2d543dab6d2ef6c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:33 p.m.