Triple
T30746416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lawh-i-Hikmat |
E782827
|
entity |
| Predicate | approximateDateOfRevelation |
P35036
|
FINISHED |
| Object | circa 1873–1874 |
—
|
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: circa 1873–1874 | Statement: [Lawh-i-Hikmat, approximateDateOfRevelation, circa 1873–1874]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDateOfRevelation Context triple: [Lawh-i-Hikmat, approximateDateOfRevelation, circa 1873–1874]
-
A.
timeOfFirstRevelation
Indicates the specific time at which the first revelation or initial disclosure of something occurred.
-
B.
dateRangeOfRevelations
chosen
Indicates the span of time during which the revelations associated with a given subject were received or occurred.
-
C.
occasionOfRevelation
Indicates the specific event, situation, or context during which a revelation or disclosure took place.
-
D.
deliveredFirstRevelationTo
Indicates that one entity was the initial recipient of a first divine, prophetic, or otherwise foundational revelation communicated by another entity.
-
E.
basedOnRevelationOf
Indicates that something (such as a belief, decision, or action) is grounded in or derived from a specific revelation or disclosed information.
- 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: April 29, 2026, 8:38 p.m.