Triple
T37646045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devanampiya Tissa |
E937039
|
entity |
| Predicate | meaningOfTitleDevanampiya |
P4542
|
FINISHED |
| Object | Beloved of the Gods |
—
|
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: Beloved of the Gods | Statement: [Devanampiya Tissa, meaningOfTitleDevanampiya, Beloved of the Gods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningOfTitleDevanampiya Context triple: [Devanampiya Tissa, meaningOfTitleDevanampiya, Beloved of the Gods]
-
A.
MahaMeans
Indicates that one entity is the definition, meaning, or semantic equivalent of the term “Maha.”
-
B.
devotionalTitle
Indicates that one entity serves as the devotional or religiously themed title associated with another entity.
-
C.
titleMeaning
chosen
Indicates that one entity expresses or explains the meaning, significance, or interpretation of another entity’s title.
-
D.
templeTitleOf
Indicates that one entity is the formal religious or ceremonial title held by another entity within a temple or sacred context.
-
E.
oniMeaning
Indicates that one entity expresses or conveys the 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.