Triple
T3963803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isra |
E85966
|
entity |
| Predicate | hasSpiritualMeaning |
P6456
|
FINISHED |
| Object | journey of the soul toward God |
—
|
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: journey of the soul toward God | Statement: [Isra, hasSpiritualMeaning, journey of the soul toward God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpiritualMeaning Context triple: [Isra, hasSpiritualMeaning, journey of the soul toward God]
-
A.
hasSpiritualDimension
chosen
Indicates that something possesses or involves a non-material, spiritual, or transcendent aspect or quality.
-
B.
hasSpiritualSource
Indicates that something originates from, is derived from, or is fundamentally grounded in a spiritual or non-material source.
-
C.
hasSpiritualHead
Indicates that one entity serves as the primary religious or spiritual leader or authority for another entity.
-
D.
hasParticularSignificanceFor
Indicates that something holds a special, notable, or contextually important relevance or impact for a particular entity or situation.
-
E.
hasLiteralMeaning
Indicates that one entity expresses the direct, explicit meaning or sense of another entity (such as a word, phrase, or symbol).
- 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_69aed93a96908190bcbdbfa718f155bd |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefba878a48190a2e234d775215938 |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef8efcf3c81908ccf61d9ce26b0c0 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:31 p.m.