Triple
T26725159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jain Agamas |
E673817
|
entity |
| Predicate | areCanonicalScripturesOf |
P60571
|
FINISHED |
| Object | Jainism |
—
|
NE NERFINISHED |
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: Jainism | Statement: [Jain Agamas, areCanonicalScripturesOf, Jainism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areCanonicalScripturesOf Context triple: [Jain Agamas, areCanonicalScripturesOf, Jainism]
-
A.
regardedAsScriptureBy
Indicates that something is considered to be sacred scripture or canonical religious text by a particular person, group, or tradition.
-
B.
recognizesScripturesFrom
Indicates that one entity acknowledges or accepts certain scriptures as authoritative or valid based on another entity as their source or origin.
-
C.
hasScripture
Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
-
D.
canonizedScriptureIn
Indicates that a text or scripture has been formally recognized and included as canonical within a particular religious tradition, community, or collection.
-
E.
consideredScriptureBy
chosen
Indicates that one party regards or recognizes a text or writing as sacred scripture.
- 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61809c4808190ba4c81b0eb702eee |
completed | May 2, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:42 a.m.