Triple
T38079585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuṣita |
E950814
|
entity |
| Predicate | positionInDesireHeavens |
P201630
|
FINISHED |
| Object | fourth heaven of the desire 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: fourth heaven of the desire realm | Statement: [Tuṣita, positionInDesireHeavens, fourth heaven of the desire realm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInDesireHeavens Context triple: [Tuṣita, positionInDesireHeavens, fourth heaven of the desire realm]
-
A.
positionOnPredestination
Indicates a stance or belief an entity holds regarding the doctrine or concept of predestination.
-
B.
eschatologicalLocation
Indicates the ultimate or final spiritual/afterlife state or place associated with an entity in an eschatological framework.
-
C.
positionRelativeToDeity
Indicates the spatial or hierarchical position an entity holds in relation to a specified deity.
-
D.
positionOnPurgatory
Indicates the relative location or rank of an entity within the structure or levels of Purgatory.
-
E.
positionOnDeity
Indicates the stance, view, or doctrinal position that an entity holds regarding a particular deity.
- 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a000efe971081909de03f875a7ad6cc |
completed | May 10, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_6a000c4ffe788190a5757af60aadd9f3 |
completed | May 10, 2026, 4:40 a.m. |
| PDg | Predicate description generation | batch_6a000efdbe948190b4bfa9871aa1a7ee |
completed | May 10, 2026, 4:52 a.m. |
Created at: May 3, 2026, 4:21 p.m.