Triple
T1433667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zamzam Well |
E30507
|
entity |
| Predicate | waterDistribution |
P4103
|
FINISHED |
| Object | pumped to coolers around Masjid al-Haram |
—
|
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: pumped to coolers around Masjid al-Haram | Statement: [Zamzam Well, waterDistribution, pumped to coolers around Masjid al-Haram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterDistribution Context triple: [Zamzam Well, waterDistribution, pumped to coolers around Masjid al-Haram]
-
A.
waterInfrastructure
chosen
Indicates the existence, development, or management of systems and facilities that supply, store, treat, or distribute water between entities.
-
B.
waterUse
Indicates the amount or manner in which water is consumed, utilized, or withdrawn by an entity or activity.
-
C.
waterAllocatedTo
Indicates that a specified amount or portion of water has been designated or assigned for use by a particular entity, location, or purpose.
-
D.
waterSource
Indicates that one entity serves as the source or provider of water for another entity.
-
E.
sourceOfWaterSupply
Indicates that one entity serves as the origin or provider of another entity’s water supply.
- 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_69a498fc69ec8190b61722bd4b67c4d2 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c500a9888190a16fbb1ec97a79c9 |
completed | March 1, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69a4c4771c9481908ae47c959debbe77 |
completed | March 1, 2026, 10:57 p.m. |
Created at: March 1, 2026, 8 p.m.