Triple
T13451608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lote Tree of the Utmost Boundary |
E320619
|
entity |
| Predicate | atItAngelGabrielStops |
P109996
|
FINISHED |
| Object | Miʿrāj ascent |
—
|
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: Miʿrāj ascent | Statement: [Lote Tree of the Utmost Boundary, atItAngelGabrielStops, Miʿrāj ascent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: atItAngelGabrielStops Context triple: [Lote Tree of the Utmost Boundary, atItAngelGabrielStops, Miʿrāj ascent]
-
A.
revelationAngel
Indicates that an angel is the one who delivers or mediates a divine revelation to someone or about something.
-
B.
commandedByAngelTo
Indicates that an entity is instructed or directed to perform an action or adopt a state as a result of a command given by an angel.
-
C.
angelicHierarchy
Indicates a hierarchical relationship in which one angelic being holds a higher or lower rank or order relative to another within a structured celestial order.
-
D.
angelicRank
Indicates the hierarchical rank or level an angel holds within a system of angelic orders.
-
E.
associatedWithArchangelName
Indicates that something has a connection or linkage to a specific archangel’s name.
- F. None of above. chosen
Provenance (4 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaefae85481909e6a59797cbb25e7 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadcce5a808190847f2a7833b67a5a |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:41 p.m.