Triple
T35981067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dzogchen Monastery |
E1040562
|
entity |
| Predicate | foundingTitleHolder |
P199006
|
FINISHED |
| Object | 1st Dzogchen Rinpoche |
—
|
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: 1st Dzogchen Rinpoche | Statement: [Dzogchen Monastery, foundingTitleHolder, 1st Dzogchen Rinpoche]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingTitleHolder Context triple: [Dzogchen Monastery, foundingTitleHolder, 1st Dzogchen Rinpoche]
-
A.
founderTitle
Indicates the formal role or title held by a person in their capacity as a founder of an organization or entity.
-
B.
foundedTitle
Indicates that an entity established or created another entity that holds a particular title or official designation.
-
C.
founderHonorificTitle
Indicates that an entity holds an honorific or ceremonial title specifically in their capacity as a founder.
-
D.
founderHonorific
Indicates that an honorific title or respectful designation is used when referring to the founder in this relationship.
-
E.
foundingLeaderOf
Indicates that an entity is the primary founder who established and initially led another entity, such as an organization, movement, or institution.
- 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
| PDg | Predicate description generation | batch_69ff1a95b6fc81909331bb03e263b5b9 |
completed | May 9, 2026, 11:29 a.m. |
Created at: May 3, 2026, 4:07 p.m.