Triple
T37946570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fourth Buddhist Council (Theravada) |
E946621
|
entity |
| Predicate | mainMonasticCommunity |
P74629
|
FINISHED |
| Object | Mahavihara monks |
—
|
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: Mahavihara monks | Statement: [Fourth Buddhist Council (Theravada), mainMonasticCommunity, Mahavihara monks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainMonasticCommunity Context triple: [Fourth Buddhist Council (Theravada), mainMonasticCommunity, Mahavihara monks]
-
A.
monasteryOrder
Indicates that a monastery belongs to, follows, or is affiliated with a particular religious order.
-
B.
monasticComponent
Indicates that something is a structural or functional part of a monastic institution or community.
-
C.
hasMonasticCommunities
chosen
Indicates that an entity possesses, hosts, or is associated with one or more monastic communities.
-
D.
monasticResidence
Indicates that one entity serves as the place of residence for a monastic individual or community.
-
E.
monastery
Indicates that an entity is or functions as a monastery, typically a religious community or building where monastics live and practice.
- 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_69f76ef64cf08190ad3e1114b62aac67 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.