Triple
T26199096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assamese Vaishnavite monasteries (Sattras) |
E655183
|
entity |
| Predicate | monasticMember |
P37071
|
FINISHED |
| Object | bhakat |
—
|
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: bhakat | Statement: [Assamese Vaishnavite monasteries (Sattras), monasticMember, bhakat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monasticMember Context triple: [Assamese Vaishnavite monasteries (Sattras), monasticMember, bhakat]
-
A.
roleInMonasticism
chosen
Indicates the specific function, position, or status an entity holds within a monastic community or tradition.
-
B.
monasticLife
Indicates a relationship where an entity lives according to monastic rules, practices, and commitments, typically within a religious community.
-
C.
monasticResidence
Indicates that one entity serves as the place of residence for a monastic individual or community.
-
D.
monasteryOrder
Indicates that a monastery belongs to, follows, or is affiliated with a particular religious order.
-
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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60cd9e50481908d1559e6ec048bc1 |
completed | May 2, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 8:47 p.m.