Triple
T32353130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newar Buddhism |
E826658
|
entity |
| Predicate | hasMonasticForm |
P196398
|
FINISHED |
| Object | quasi-monastic householder monks |
—
|
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: quasi-monastic householder monks | Statement: [Newar Buddhism, hasMonasticForm, quasi-monastic householder monks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonasticForm Context triple: [Newar Buddhism, hasMonasticForm, quasi-monastic householder monks]
-
A.
hasMonasticName
Indicates that an entity possesses a specific name adopted or assigned within a monastic or religious order.
-
B.
hasMonasticHistory
Indicates that an entity has a historical association with monastic life, institutions, or traditions.
-
C.
wasMonkOf
Indicates that a person was a member or monk belonging to a particular religious order, monastery, or monastic community.
-
D.
hasMonasticComplexFeature
Indicates that a monastic complex includes or is characterized by a particular architectural or functional feature.
-
E.
hasMonasticNameMeaning
Indicates that an entity’s monastic name carries a specific meaning or significance.
- 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69fe30bb07d08190877539d5aa202d24 |
completed | May 8, 2026, 6:51 p.m. |
Created at: May 1, 2026, 12:49 a.m.