Triple
T30584020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buddha’s descent from Tavatimsa heaven |
E778455
|
entity |
| Predicate | locationOfDescent |
P202886
|
FINISHED |
| Object | Sankassa |
—
|
NE NERFINISHED |
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: Sankassa | Statement: [Buddha’s descent from Tavatimsa heaven, locationOfDescent, Sankassa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfDescent Context triple: [Buddha’s descent from Tavatimsa heaven, locationOfDescent, Sankassa]
-
A.
descentFrom
Indicates that one entity is a descendant of another, typically through a lineage or ancestral relationship.
-
B.
claimedDescentFrom
Indicates that one entity asserts or maintains that it is descended from, or originates genealogically from, another entity.
-
C.
ofDescent
Indicates a genealogical or ancestral relationship, specifying that one entity descends from or originates from another.
-
D.
presentDayLocationOfDescendants
Indicates the current geographic location where the descendants of a specified person or group are found.
-
E.
descentSystem
Indicates the kinship or inheritance pattern through which lineage, membership, or rights are traced (e.g., matrilineal, patrilineal, or bilateral).
- 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00cbae75988190974f5b45a2e62326 |
completed | May 10, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_6a00cabe4c5881909cca5efbe494e0d1 |
completed | May 10, 2026, 6:13 p.m. |
| PDg | Predicate description generation | batch_6a00cbad83e88190ba792d3172370f63 |
completed | May 10, 2026, 6:17 p.m. |
Created at: April 29, 2026, 8:23 p.m.