Triple
T33039873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cakrasaṃvara |
E845430
|
entity |
| Predicate | tibetanWylie |
P125122
|
FINISHED |
| Object | ’khor lo bde mchog |
—
|
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: ’khor lo bde mchog | Statement: [Cakrasaṃvara, tibetanWylie, ’khor lo bde mchog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tibetanWylie Context triple: [Cakrasaṃvara, tibetanWylie, ’khor lo bde mchog]
-
A.
nameInTibetan
chosen
Indicates that an entity’s name is expressed or written in the Tibetan language.
-
B.
equivalentInTibet
Indicates that two entities are considered equivalent or correspond to each other within the context of Tibet.
-
C.
WadeGilesForm
Indicates that one entity is the Wade–Giles romanized form corresponding to another entity’s written or spoken Chinese form.
-
D.
formerTransliteration
Indicates that one transliteration was previously used for an entity but has since been replaced by a different transliteration.
-
E.
transliterationTarget
Indicates that one entity is the target script or form into which another entity is transliterated.
- 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_69f34951348c8190b56746b0a7018182 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:24 a.m.