Triple
T36700132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gomukha |
E906202
|
entity |
| Predicate | associatedTirthankaraNumber |
—
|
GENERATED |
| Object | 1 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedTirthankaraNumber Context triple: [Gomukha, associatedTirthankaraNumber, 1]
-
A.
associatedWithTirthankara
Indicates a relationship where an entity has a connection, link, or relevance to a Tirthankara.
-
B.
numberOfTirthankaras
chosen
Indicates the specific count of Tirthankaras associated with or attributed to an entity.
-
C.
earlyTirthankara
Indicates that the subject is recognized as one of the earlier Tirthankaras in the traditional chronological sequence.
-
D.
lastTirthankara
Indicates that the subject is the final or most recent Tirthankara in a recognized sequence of Tirthankaras.
-
E.
predecessorTirthankara
Indicates that one Tirthankara directly precedes another in the ordered sequence of Tirthankaras.
- F. None of above.
Provenance (1 batch)
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. |
Created at: May 3, 2026, 4:12 p.m.