Triple
T24283054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Night of Destiny |
E605594
|
entity |
| Predicate | eventFor |
P49138
|
FINISHED |
| Object | first revelation to Prophet Muhammad |
—
|
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: first revelation to Prophet Muhammad | Statement: [Night of Destiny, eventFor, first revelation to Prophet Muhammad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventFor Context triple: [Night of Destiny, eventFor, first revelation to Prophet Muhammad]
-
A.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
B.
eventUse
Indicates that an event involves the use or utilization of a particular entity (e.g., a resource, tool, or method) as part of its occurrence.
-
C.
eventName
Indicates the specific label or title assigned to identify an event within a system or context.
-
D.
event
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
-
E.
mainEventFor
chosen
Indicates that one event is the primary or central event associated with another entity, such as a context, grouping, or larger occurrence.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f53a8448190b66f6a97544bacc1 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:08 a.m.