Triple
T1433661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zamzam Well |
E30507
|
entity |
| Predicate | statusInIslam |
P27136
|
FINISHED |
| Object | highly revered |
—
|
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: highly revered | Statement: [Zamzam Well, statusInIslam, highly revered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInIslam Context triple: [Zamzam Well, statusInIslam, highly revered]
-
A.
statusInIslamicTradition
chosen
Indicates the recognized standing, role, or level of esteem an entity holds within Islamic religious, cultural, or scholarly tradition.
-
B.
normativeStatusInIslam
Indicates the evaluative ruling or status that Islamic law or ethics assigns to an action, practice, or state (e.g., obligatory, recommended, permissible, disliked, or forbidden).
-
C.
positionInIslam
Indicates the specific religious role, rank, or status an entity holds within the context of Islam.
-
D.
quranicStatus
Indicates the status or classification of something in relation to its recognition, treatment, or role within the Quran.
-
E.
statusInChristianity
Indicates the recognized role, standing, or significance that something or someone holds within Christian belief, practice, or tradition.
- 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.