Triple
T34131149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sammed Shikhar |
E875426
|
entity |
| Predicate | numberOfTirthankarasAttainingMoksha |
P11021
|
FINISHED |
| Object | 20 |
—
|
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: 20 | Statement: [Sammed Shikhar, numberOfTirthankarasAttainingMoksha, 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfTirthankarasAttainingMoksha Context triple: [Sammed Shikhar, numberOfTirthankarasAttainingMoksha, 20]
-
A.
numberOfTirthankaras
chosen
Indicates the specific count of Tirthankaras associated with or attributed to an entity.
-
B.
lastTirthankara
Indicates that the subject is the final or most recent Tirthankara in a recognized sequence of Tirthankaras.
-
C.
attainedMokshaFrom
Indicates that an entity achieved spiritual liberation (moksha) as a result of or through the agency, guidance, or context of another entity.
-
D.
earlyTirthankara
Indicates that the subject is recognized as one of the earlier Tirthankaras in the traditional chronological sequence.
-
E.
associatedWithTirthankara
Indicates a relationship where an entity has a connection, link, or relevance to a Tirthankara.
- 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:53 a.m.