Triple
T24643942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajab |
E610052
|
entity |
| Predicate | consideredSacredIn |
P21134
|
FINISHED |
| Object | Qur’anic tradition |
—
|
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: Qur’anic tradition | Statement: [Rajab, consideredSacredIn, Qur’anic tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consideredSacredIn Context triple: [Rajab, consideredSacredIn, Qur’anic tradition]
-
A.
sacredTo
Indicates that one entity is regarded as holy, revered, or dedicated in honor of another entity, such as a deity, person, or concept.
-
B.
sacredStatus
chosen
Indicates that something holds a revered, holy, or religiously significant status within a particular belief system or tradition.
-
C.
hasReligiousSignificanceVia
Indicates that something holds religious significance specifically by means of, or through the mediation of, another entity, event, or context.
-
D.
worshippedIn
Indicates that a particular deity, figure, or object of reverence is the focus of religious or spiritual worship within a specified place or context.
-
E.
veneratedBy
Indicates that one entity is regarded with deep respect, reverence, or worship by another entity.
- 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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f40db2b5e08190bb55d02a4ceba306 |
completed | May 1, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d2b20881908dcc3b15cbe3e5b0 |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:33 a.m.