Triple
T21562077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parshvanatha |
E532061
|
entity |
| Predicate | attainedMoksha |
P60492
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Parshvanatha, attainedMoksha, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attainedMoksha Context triple: [Parshvanatha, attainedMoksha, true]
-
A.
attainedKevalaJnana
Indicates that an entity has achieved Kevala Jnana, the state of absolute or perfect knowledge.
-
B.
viewOnMoksha
Indicates the stance, interpretation, or doctrinal position that one entity holds regarding the concept or state of moksha (liberation).
-
C.
hasSamadhi
Indicates that an entity possesses or has attained the state of samadhi (deep meditative absorption or spiritual concentration) in relation to another context or state.
-
D.
tookSannyasaFrom
Indicates that one entity formally renounced worldly life and accepted the monastic or ascetic order under the guidance or authority of another entity.
-
E.
spiritualAchievement
chosen
Indicates the attainment or realization of a significant level of spiritual growth, insight, or enlightenment by an entity.
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eed2e3e2348190b5c3b66cdc871e6e |
completed | April 27, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:29 p.m.