Triple
T19597786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jyotir Peeth |
E470391
|
entity |
| Predicate | governsMonasticLineage |
P136421
|
FINISHED |
| Object | northern Shankaracharya lineage |
—
|
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: northern Shankaracharya lineage | Statement: [Jyotir Peeth, governsMonasticLineage, northern Shankaracharya lineage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsMonasticLineage Context triple: [Jyotir Peeth, governsMonasticLineage, northern Shankaracharya lineage]
-
A.
hasMonasticHistory
Indicates that an entity has a historical association with monastic life, institutions, or traditions.
-
B.
monasteryAffiliation
Indicates a relationship where an entity is formally associated with, belongs to, or is under the authority of a particular monastery.
-
C.
monasticTradition
Indicates that an entity follows, belongs to, or is characterized by a particular monastic rule, lineage, or way of religious life.
-
D.
monasteryOrder
Indicates that a monastery belongs to, follows, or is affiliated with a particular religious order.
-
E.
hasMonasticName
Indicates that an entity possesses a specific name adopted or assigned within a monastic or religious order.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6407c52c081908704d3a4dd6e853b |
completed | April 20, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e5174b060c81908937ff9ff7fce611 |
completed | April 19, 2026, 5:56 p.m. |
Created at: April 10, 2026, 1:43 p.m.