Triple

T14550260
Position Surface form Disambiguated ID Type / Status
Subject Cave Hira E341395 entity
Predicate firstRevelationContent P8497 FINISHED
Object verses 1–5 of Surah al-Alaq 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: verses 1–5 of Surah al-Alaq | Statement: [Cave Hira, firstRevelationContent, verses 1–5 of Surah al-Alaq]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: firstRevelationContent
Context triple: [Cave Hira, firstRevelationContent, verses 1–5 of Surah al-Alaq]
  • A. firstRevelationNear
    Indicates that an entity’s initial revelation, disclosure, or divine communication occurred in the vicinity of a specified place or reference entity.
  • B. firstRevelationPlace chosen
    Indicates the location where something (typically a text, message, or revelation) was first revealed or disclosed.
  • C. occasionOfRevelation
    Indicates the specific event, situation, or context during which a revelation or disclosure took place.
  • D. firstPublicRevelationsBy
    Indicates that the subject is the entity that first publicly revealed or disclosed the object.
  • E. receivesRevelation
    Indicates that one entity is the recipient of a divine, supernatural, or otherwise profound revelation originating from another source.
  • 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_69d822db9c8481908213ceb39585f792 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb2ed2b4c8190945bd26531c71f1f completed April 14, 2026, 9:34 p.m.
PD Predicate disambiguation batch_69de5c546c7081909e27d504ec360c5c completed April 14, 2026, 3:25 p.m.
Created at: April 10, 2026, 1:23 a.m.