Triple
T35980969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yeshe Tsogyal |
E1040560
|
entity |
| Predicate | lineageHolderOf |
P115355
|
FINISHED |
| Object | Nyingma tradition |
—
|
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: Nyingma tradition | Statement: [Yeshe Tsogyal, lineageHolderOf, Nyingma tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineageHolderOf Context triple: [Yeshe Tsogyal, lineageHolderOf, Nyingma tradition]
-
A.
lineageRelatedTo
Indicates a relationship where two entities are connected through a line of descent or ancestry within the same lineage.
-
B.
lineageSystem
Indicates a hierarchical ancestry or descent relationship that traces how entities are derived from or originate through one another within a system.
-
C.
lineagePosition
Indicates the relative placement or rank of an entity within a lineage or ancestral chain.
-
D.
sourceOfLineageFor
chosen
Indicates that one entity serves as the origin or ancestral source from which another entity’s lineage is derived.
-
E.
titleHolderLineage
Indicates the succession relationship showing which entity inherited or held a title from which predecessor in a lineage.
- 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:07 p.m.