Triple
T2280909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahavira |
E51276
|
entity |
| Predicate | asceticPracticeDuration |
P36229
|
FINISHED |
| Object | 12 years |
—
|
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: 12 years | Statement: [Mahavira, asceticPracticeDuration, 12 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: asceticPracticeDuration Context triple: [Mahavira, asceticPracticeDuration, 12 years]
-
A.
timePeriodOfWorship
Indicates the specific time period during which the worship activity takes place or is observed.
-
B.
tookSannyasaFrom
Indicates that one entity formally renounced worldly life and accepted the monastic or ascetic order under the guidance or authority of another entity.
-
C.
yearOfSannyasa
Indicates the specific year in which an individual formally took sannyasa (renounced worldly life and entered the renounced order).
-
D.
tookReligiousVowsOn
Indicates that an entity formally committed to religious vows on a specific date or occasion.
-
E.
spiritualDiscipline
Indicates a relationship where an entity engages in or practices a form of spiritual training, exercise, or regimen aimed at cultivating spiritual growth or character.
- 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_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. |
| PDg | Predicate description generation | batch_69abbe4368a88190956bc9ee89c0fd1f |
completed | March 7, 2026, 5:57 a.m. |
Created at: March 4, 2026, 7:48 p.m.