Triple
T21232767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krida Khanda |
E523263
|
entity |
| Predicate | hasScripturalFunction |
P94961
|
FINISHED |
| Object | narrative of Ganesha’s deeds |
—
|
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: narrative of Ganesha’s deeds | Statement: [Krida Khanda, hasScripturalFunction, narrative of Ganesha’s deeds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScripturalFunction Context triple: [Krida Khanda, hasScripturalFunction, narrative of Ganesha’s deeds]
-
A.
hasScripturalRole
Indicates that an entity holds a specific role, function, or position within a scriptural or religious text.
-
B.
scripturalFunction
chosen
Indicates the role or purpose that a text or passage serves within a scriptural or religious context.
-
C.
hasScripture
Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
-
D.
biblicalFunction
Indicates that one entity serves a particular role, duty, or purpose in a biblical or scriptural context in relation to another entity.
-
E.
hasSacredFunction
Indicates that something serves a religious or holy role, purpose, or duty within a sacred 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734b1524c8190a77eaf2fabd601c3 |
completed | April 21, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:45 p.m.