Triple
T33613357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayt Allah |
E861047
|
entity |
| Predicate | holinessStatusInIslam |
P169088
|
FINISHED |
| Object | holiest site |
—
|
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: holiest site | Statement: [Bayt Allah, holinessStatusInIslam, holiest site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holinessStatusInIslam Context triple: [Bayt Allah, holinessStatusInIslam, holiest site]
-
A.
holinessRankInIslam
chosen
Indicates the relative level of sacredness or spiritual importance an entity holds within Islamic belief or practice.
-
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.
statusInIslamicTradition
Indicates the recognized standing, role, or level of esteem an entity holds within Islamic religious, cultural, or scholarly tradition.
-
D.
scripturalStatusInIslam
Indicates the status or standing of something within Islamic scripture or religious texts.
-
E.
positionInIslam
Indicates the specific religious role, rank, or status an entity holds within the context of Islam.
- 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f7e459708190b0a31f51946c630f |
completed | May 3, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:41 a.m.