Triple
T2280915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahavira |
E51276
|
entity |
| Predicate | placeOfKevalaJnana |
P9185
|
FINISHED |
| Object | on the banks of the Rijupalika River |
—
|
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: on the banks of the Rijupalika River | Statement: [Mahavira, placeOfKevalaJnana, on the banks of the Rijupalika River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfKevalaJnana Context triple: [Mahavira, placeOfKevalaJnana, on the banks of the Rijupalika River]
-
A.
spiritualCenterOf
Indicates that one entity serves as the primary locus or focal point of spiritual life, practice, or significance for another entity or group.
-
B.
revelationPlace
chosen
Indicates the place or location where a revelation, disclosure, or revealing event occurs.
-
C.
firstRevelationPlace
Indicates the location where something (typically a text, message, or revelation) was first revealed or disclosed.
-
D.
placeOfMonasticFoundation
Indicates the location where a monastic community or monastery was originally established or founded.
-
E.
cultLocation
Indicates that a cult or religious group is based in, practices in, or is primarily associated with a particular location.
- 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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc21ac3d48190abef254e1c3f45e8 |
completed | March 7, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69abbdb9aa3c819088d0316c5269a1c2 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.