Triple
T35211636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siyam Nikaya |
E1016694
|
entity |
| Predicate | hasMonasticRole |
P37071
|
FINISHED |
| Object | Mahanayaka Thero |
—
|
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: Mahanayaka Thero | Statement: [Siyam Nikaya, hasMonasticRole, Mahanayaka Thero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonasticRole Context triple: [Siyam Nikaya, hasMonasticRole, Mahanayaka Thero]
-
A.
roleInMonasticism
chosen
Indicates the specific function, position, or status an entity holds within a monastic community or tradition.
-
B.
hasMonasticForm
Indicates that an entity possesses or is associated with a specific monastic form, style, or mode of religious life.
-
C.
monasticRequirement
Indicates that one entity imposes, specifies, or embodies a rule, obligation, or condition that must be fulfilled within a monastic or religious order.
-
D.
wasMonkOf
Indicates that a person was a member or monk belonging to a particular religious order, monastery, or monastic community.
-
E.
hasMonasticName
Indicates that an entity possesses a specific name adopted or assigned 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fef5cf8da881908260ec633830375d |
completed | May 9, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69fef455e40481909861c82007b79bc0 |
completed | May 9, 2026, 8:46 a.m. |
Created at: May 3, 2026, 4:02 p.m.