Triple
T13430037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nyingma school |
E313581
|
entity |
| Predicate | hasMonasticComponent |
P74629
|
FINISHED |
| Object | Nyingma monasteries |
—
|
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: Nyingma monasteries | Statement: [Nyingma school, hasMonasticComponent, Nyingma monasteries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonasticComponent Context triple: [Nyingma school, hasMonasticComponent, Nyingma monasteries]
-
A.
hasMonasticHistory
Indicates that an entity has a historical association with monastic life, institutions, or traditions.
-
B.
hasMonasticName
Indicates that an entity possesses a specific name adopted or assigned within a monastic or religious order.
-
C.
hasMonasticCommunities
chosen
Indicates that an entity possesses, hosts, or is associated with one or more monastic communities.
-
D.
containsMonastery
Indicates that one entity includes or encompasses a monastery within its boundaries or composition.
-
E.
monasticRequirement
Indicates that one entity imposes, specifies, or embodies a rule, obligation, or condition that must be fulfilled within a monastic or religious order.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaed304ac8190a8021f749de8164c |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.