Triple
T18577812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plum Village Community of Engaged Buddhism |
E454028
|
entity |
| Predicate | hasMonasticBranch |
P74629
|
FINISHED |
| Object | 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: monks | Statement: [Plum Village Community of Engaged Buddhism, hasMonasticBranch, monks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonasticBranch Context triple: [Plum Village Community of Engaged Buddhism, hasMonasticBranch, monks]
-
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.
monasteryAffiliation
Indicates a relationship where an entity is formally associated with, belongs to, or is under the authority of a particular monastery.
-
D.
hasMonasticCommunities
chosen
Indicates that an entity possesses, hosts, or is associated with one or more monastic communities.
-
E.
wasMonkOf
Indicates that a person was a member or monk belonging to a particular religious order, monastery, or monastic community.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e543cd6a3c8190b38059e71ec3f7b2 |
completed | April 19, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.