Triple
T19077704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quran |
E466946
|
entity |
| Predicate | modeOfRevelation |
P11155
|
FINISHED |
| Object | oral recitation |
—
|
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: oral recitation | Statement: [Quran, modeOfRevelation, oral recitation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modeOfRevelation Context triple: [Quran, modeOfRevelation, oral recitation]
-
A.
hasModeOfRevelation
chosen
Indicates the manner or channel through which something is revealed, communicated, or made known.
-
B.
occasionOfRevelation
Indicates the specific event, situation, or context during which a revelation or disclosure took place.
-
C.
basedOnRevelationOf
Indicates that something (such as a belief, decision, or action) is grounded in or derived from a specific revelation or disclosed information.
-
D.
receivesRevelation
Indicates that one entity is the recipient of a divine, supernatural, or otherwise profound revelation originating from another source.
-
E.
receivesRevelationFrom
Indicates that one entity is the recipient of a revelation, message, or disclosed knowledge that originates from 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e5591081908a4f8e4b2011b408 |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.