Triple
T38157042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cāturmahārājika heaven |
E952912
|
entity |
| Predicate | destinyType |
P93492
|
FINISHED |
| Object | fortunate rebirth realm |
—
|
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: fortunate rebirth realm | Statement: [Cāturmahārājika heaven, destinyType, fortunate rebirth realm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destinyType Context triple: [Cāturmahārājika heaven, destinyType, fortunate rebirth realm]
-
A.
ascendancyClassType
Indicates the specific subclass or specialization category to which an entity’s ascendancy belongs.
-
B.
destinedRole
Indicates that an entity is assigned or fated to fulfill a particular role or function, typically in a future or predetermined context.
-
C.
eschatologicalDestiny
chosen
Indicates the ultimate fate or final outcome that is believed to await an entity within a religious or philosophical view of the end times.
-
D.
soulbindTreeType
Indicates a relationship where an entity is associated with, or categorized under, a specific type of soulbind tree.
-
E.
ascendancyClass
Indicates a hierarchical or rank-based classification that specifies an entity’s superior or dominant status relative to others.
- 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:21 p.m.