Triple
T37646050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devanampiya Tissa |
E937039
|
entity |
| Predicate | introducedToBuddhismBy |
P192536
|
FINISHED |
| Object | Mahinda |
—
|
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: Mahinda | Statement: [Devanampiya Tissa, introducedToBuddhismBy, Mahinda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedToBuddhismBy Context triple: [Devanampiya Tissa, introducedToBuddhismBy, Mahinda]
-
A.
receivedBuddhismFrom
chosen
Indicates that one entity obtained or adopted Buddhism through the influence, teaching, or transmission from another entity.
-
B.
associatedBuddha
Indicates a relationship where something is linked or connected to a particular Buddha, such as being attributed to, dedicated to, or representing that Buddha.
-
C.
broughtBuddhistTextsTo
Indicates that one entity transported or introduced Buddhist texts to another entity or location.
-
D.
introducedToIndiaBy
Indicates that something was brought or made known to India by a particular agent, source, or intermediary.
-
E.
BuddhistTradition
Indicates that an entity follows, embodies, or is associated with Buddhist religious, philosophical, or cultural traditions.
- 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_69fef3ceef648190b58027c93d757438 |
completed | May 9, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69fef359da2c819091a034387b08821f |
completed | May 9, 2026, 8:42 a.m. |
Created at: May 3, 2026, 4:18 p.m.