Triple
T36208297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorje Drak Monastery |
E1047460
|
entity |
| Predicate | hasMonasticCollege |
P164061
|
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, hasMonasticCollege, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonasticCollege Context triple: [Dorje Drak Monastery, hasMonasticCollege, yes]
-
A.
monasticColleges
chosen
Indicates that there is a relationship involving monastic colleges, typically linking an entity to the monastic educational or residential institutions with which it is associated.
-
B.
hasMonasticHistory
Indicates that an entity has a historical association with monastic life, institutions, or traditions.
-
C.
hasMonasticCommunities
Indicates that an entity possesses, hosts, or is associated with one or more monastic communities.
-
D.
hasMonasticComplexFeature
Indicates that a monastic complex includes or is characterized by a particular architectural or functional feature.
-
E.
containsMonastery
Indicates that one entity includes or encompasses a monastery within its boundaries or composition.
- 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_69f76e4214748190a76c986d2a1838c2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff48199b1c8190bb05872f8a4f4673 |
completed | May 9, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69ff4746b1cc8190854f70a124df7d04 |
completed | May 9, 2026, 2:40 p.m. |
Created at: May 3, 2026, 4:09 p.m.