Triple
T13886068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charitropakhyan |
E333845
|
entity |
| Predicate | positionInDasamGranth |
P112248
|
FINISHED |
| Object | later section of Dasam Granth |
—
|
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: later section of Dasam Granth | Statement: [Charitropakhyan, positionInDasamGranth, later section of Dasam Granth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInDasamGranth Context triple: [Charitropakhyan, positionInDasamGranth, later section of Dasam Granth]
-
A.
positionInGuruGranthSahib
Indicates the specific location or ordering of a referenced element within the text of the Guru Granth Sahib.
-
B.
positionInVeda
Indicates the specific location or ordering of a referenced element within the structure of a Vedic text.
-
C.
positionWithinAnandSahib
Indicates that one entity occupies a specific location or segment within the Anand Sahib text or structure.
-
D.
positionInJainTradition
Indicates the role, rank, or status an entity holds within the hierarchy or lineage of the Jain religious tradition.
-
E.
positionInSaptarishi
Indicates the specific place or ordering that an entity occupies within the Saptarishi group.
- F. None of above. chosen
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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a101488190bd790b28033d38b9 |
completed | April 14, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69de05972f3881909977b4c843984f88 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239524688190a0f2408c239cfcaa |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:15 p.m.