Triple
T34069832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buddhapālita |
E873731
|
entity |
| Predicate | inTibetanTraditionClassifiedAs |
P70824
|
FINISHED |
| Object | Prāsaṅgika |
—
|
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: Prāsaṅgika | Statement: [Buddhapālita, inTibetanTraditionClassifiedAs, Prāsaṅgika]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inTibetanTraditionClassifiedAs Context triple: [Buddhapālita, inTibetanTraditionClassifiedAs, Prāsaṅgika]
-
A.
roleInTibet
Indicates that an entity holds or has held a specific role, position, or function within the context of Tibet.
-
B.
traditionClassification
chosen
Indicates how a given item, practice, or concept is categorized within a particular tradition or system of traditions.
-
C.
BuddhistTradition
Indicates that an entity follows, embodies, or is associated with Buddhist religious, philosophical, or cultural traditions.
-
D.
equivalentInTibet
Indicates that two entities are considered equivalent or correspond to each other within the context of Tibet.
-
E.
belongsToMacroTradition
Indicates that one entity is classified as part of, or originating from, a broader overarching tradition or school.
- 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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70bccf4c88190a424809033d25e18 |
completed | May 3, 2026, 8:48 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:52 a.m.