Triple
T2303147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tirthankaras |
E51776
|
entity |
| Predicate | roleInReligion |
P9873
|
FINISHED |
| Object | spiritual guide |
—
|
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: spiritual guide | Statement: [Tirthankaras, roleInReligion, spiritual guide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInReligion Context triple: [Tirthankaras, roleInReligion, spiritual guide]
-
A.
positionInReligion
Indicates the specific role, rank, or office an entity holds within a religious organization or tradition.
-
B.
religiousFunction
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
-
C.
bearerReligion
Indicates that a bearer (such as a person or entity) adheres to, practices, or is associated with a particular religion.
-
D.
religiousTarget
Indicates that an action, policy, or behavior is directed at someone or something specifically because of their religion or religious affiliation.
-
E.
theologicalRole
chosen
Indicates a relationship where an entity holds or is assigned a specific function, office, or status within a theological or religious framework.
- 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.