Triple
T5260338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raphael (archangel) |
E118806
|
entity |
| Predicate | angelicHierarchy |
P62584
|
FINISHED |
| Object | archangel order |
—
|
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: archangel order | Statement: [Raphael (archangel), angelicHierarchy, archangel order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: angelicHierarchy Context triple: [Raphael (archangel), angelicHierarchy, archangel order]
-
A.
revelationAngel
Indicates that an angel is the one who delivers or mediates a divine revelation to someone or about something.
-
B.
associatedWithArchangelName
Indicates that something has a connection or linkage to a specific archangel’s name.
-
C.
roleInEschatology
Indicates the role or function an entity is believed to have within doctrines, narratives, or expectations about the end times or ultimate destiny of the world.
-
D.
divineAgent
Indicates that the related entity acts as a deity or supernatural agent responsible for causing or overseeing the associated event or state.
-
E.
eschatologicalOrder
Indicates the relationship of how events, beings, or realities are arranged or sequenced within an ultimate, end-times framework or final divine plan.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bcf026c8190881b6e14b962a3c9 |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd7bcabe58819096255672664513b1 |
completed | March 20, 2026, 4:54 p.m. |
Created at: March 20, 2026, 1:50 p.m.