Triple
T2303149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tirthankaras |
E51776
|
entity |
| Predicate | spiritualStatus |
P21134
|
FINISHED |
| Object | omniscient |
—
|
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: omniscient | Statement: [Tirthankaras, spiritualStatus, omniscient]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spiritualStatus Context triple: [Tirthankaras, spiritualStatus, omniscient]
-
A.
hasSpiritualDimension
Indicates that something possesses or involves a non-material, spiritual, or transcendent aspect or quality.
-
B.
hasSpiritualHead
Indicates that one entity serves as the primary religious or spiritual leader or authority for another entity.
-
C.
sacredStatus
chosen
Indicates that something holds a revered, holy, or religiously significant status within a particular belief system or tradition.
-
D.
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.
-
E.
statusInChristianity
Indicates the recognized role, standing, or significance that something or someone holds within Christian belief, practice, or tradition.
- 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_69a88b0a9f248190bcff941463d8f65a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcbabf01081908db3b42bc7c60444 |
completed | March 7, 2026, 6:54 a.m. |
| PD | Predicate disambiguation | batch_69abc58ad33c8190b8d68af41b6f5e07 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.