Triple
T28246425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ganden Monastery |
E712180
|
entity |
| Predicate | traditionalTitleOfHead |
P118741
|
FINISHED |
| Object | Ganden Tripa |
—
|
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: Ganden Tripa | Statement: [Ganden Monastery, traditionalTitleOfHead, Ganden Tripa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalTitleOfHead Context triple: [Ganden Monastery, traditionalTitleOfHead, Ganden Tripa]
-
A.
traditionalTitleOfLeader
chosen
Indicates the customary or historically recognized title used to refer to a particular leader.
-
B.
traditionalTitleGivenBy
Indicates that one entity has conferred or assigned a traditional or customary title to another entity.
-
C.
traditionalTitleOfKing
Indicates that the object is the customary or historically recognized royal title held by the king specified as the subject.
-
D.
traditionalTitle
Indicates that an entity holds or is associated with a customary or historically established title or honorific within a cultural or social tradition.
-
E.
religiousTitle
Indicates that one entity holds or is referred to by a specific religious rank, honorific, or clerical title in relation to another entity.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: April 27, 2026, 11:01 p.m.