Triple
T19314680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhaisajyaguru |
E483062
|
entity |
| Predicate | roleInTibet |
P135556
|
FINISHED |
| Object | important yidam in healing practices |
—
|
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: important yidam in healing practices | Statement: [Bhaisajyaguru, roleInTibet, important yidam in healing practices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInTibet Context triple: [Bhaisajyaguru, roleInTibet, important yidam in healing practices]
-
A.
roleInNepal
Indicates that an entity holds or has held a specific role, position, or function within the context of Nepal.
-
B.
equivalentInTibet
Indicates that two entities are considered equivalent or correspond to each other within the context of Tibet.
-
C.
nameInTibetan
Indicates that an entity’s name is expressed or written in the Tibetan language.
-
D.
roleInSikhTradition
Indicates the specific function, status, or position an entity holds within Sikh religious, cultural, or historical practices and institutions.
-
E.
roleInMonasticism
Indicates the specific function, position, or status an entity holds within a monastic community or tradition.
- 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e604cfec8c8190a118b327b1418150 |
completed | April 20, 2026, 10:49 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4e4709d4481908c280cdd2ac18977 |
completed | April 19, 2026, 2:19 p.m. |
Created at: April 10, 2026, 1:32 p.m.