Triple
T36051953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kathok lineage |
E1042832
|
entity |
| Predicate | hasMonasticSeat |
P199475
|
FINISHED |
| Object | Kathok Dorje Den (Kathok Monastery) |
—
|
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: Kathok Dorje Den (Kathok Monastery) | Statement: [Kathok lineage, hasMonasticSeat, Kathok Dorje Den (Kathok Monastery)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonasticSeat Context triple: [Kathok lineage, hasMonasticSeat, Kathok Dorje Den (Kathok Monastery)]
-
A.
wasMonkOf
Indicates that a person was a member or monk belonging to a particular religious order, monastery, or monastic community.
-
B.
hasMonasticComplexFeature
Indicates that a monastic complex includes or is characterized by a particular architectural or functional feature.
-
C.
hasMonasticName
Indicates that an entity possesses a specific name adopted or assigned within a monastic or religious order.
-
D.
hasMonasticForm
Indicates that an entity possesses or is associated with a specific monastic form, style, or mode of religious life.
-
E.
hasMonasticHistory
Indicates that an entity has a historical association with monastic life, institutions, or traditions.
- 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_69f76e2e41f8819091f9fb0536920fec |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
| PDg | Predicate description generation | batch_69ff3b323a748190827165f1cb274141 |
completed | May 9, 2026, 1:48 p.m. |
Created at: May 3, 2026, 4:07 p.m.