Triple
T11025459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rishabhanatha |
E260604
|
entity |
| Predicate | veneratedBeyondJainism |
P8505
|
FINISHED |
| Object | some Hindu traditions |
—
|
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: some Hindu traditions | Statement: [Rishabhanatha, veneratedBeyondJainism, some Hindu traditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: veneratedBeyondJainism Context triple: [Rishabhanatha, veneratedBeyondJainism, some Hindu traditions]
-
A.
viewInJainism
Indicates the specific interpretation, significance, or doctrinal understanding of something within the context of Jainism.
-
B.
veneratedBy
chosen
Indicates that one entity is regarded with deep respect, reverence, or worship by another entity.
-
C.
veneratedFor
Indicates that one entity is highly respected, honored, or revered because of a particular quality, achievement, or characteristic of another entity.
-
D.
basisOfVeneration
Indicates the reason, quality, or attribute for which something or someone is regarded with reverence or veneration.
-
E.
veneratedFigureMentioned
Indicates that a person who is highly respected or revered is explicitly referenced or mentioned in relation to another entity or context.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797bf78a48190a37b423812827d4e |
completed | April 9, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69d7440087ac8190aef2e6f6b13b2635 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:25 p.m.