Triple
T36208298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorje Drak Monastery |
E1047460
|
entity |
| Predicate | hasReincarnateLineage |
P204791
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Dorje Drak Monastery, hasReincarnateLineage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReincarnateLineage Context triple: [Dorje Drak Monastery, hasReincarnateLineage, yes]
-
A.
hasReincarnationTheme
Indicates that the subject involves or prominently features the concept of reincarnation as a central theme.
-
B.
isRelictLineage
Indicates that an entity represents a surviving remnant of an otherwise extinct evolutionary lineage.
-
C.
hasMagicLineage
Indicates that one entity is descended from, or ancestrally connected to, another through a bloodline associated with magic or supernatural powers.
-
D.
earlierIncarnationOf
Indicates that one entity is a previous incarnation or earlier life-form of another entity in a sequence of reincarnations or transformations.
-
E.
hasMultipleIncarnations
Indicates that an entity exists or appears in more than one distinct form, version, or embodiment over time or context.
- 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_69f76e4214748190a76c986d2a1838c2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:09 p.m.