Triple
T36700133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gomukha |
E906202
|
entity |
| Predicate | associatedTirthankaraName |
P95005
|
FINISHED |
| Object | Rishabhanatha |
E260604
|
NE 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: Rishabhanatha | Statement: [Gomukha, associatedTirthankaraName, Rishabhanatha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedTirthankaraName Context triple: [Gomukha, associatedTirthankaraName, Rishabhanatha]
-
A.
associatedWithTirthankara
chosen
Indicates a relationship where an entity has a connection, link, or relevance to a Tirthankara.
-
B.
earlyTirthankara
Indicates that the subject is recognized as one of the earlier Tirthankaras in the traditional chronological sequence.
-
C.
associatedBuddha
Indicates a relationship where something is linked or connected to a particular Buddha, such as being attributed to, dedicated to, or representing that Buddha.
-
D.
associatedRishi
Indicates a relationship where a given entity is linked or connected to a particular rishi (sage), typically as being attributed to, guided by, or traditionally related to that rishi.
-
E.
numberOfTirthankaras
Indicates the specific count of Tirthankaras associated with or attributed to an entity.
- F. None of above.
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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40636e6ad08190a06a044a7b91122a |
completed | June 27, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.