Triple
T34022204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Das Lakshan Parva |
E872409
|
entity |
| Predicate | day4Virtue |
P165794
|
FINISHED |
| Object | Uttam Shaucha (supreme contentment/purity) |
—
|
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: Uttam Shaucha (supreme contentment/purity) | Statement: [Das Lakshan Parva, day4Virtue, Uttam Shaucha (supreme contentment/purity)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: day4Virtue Context triple: [Das Lakshan Parva, day4Virtue, Uttam Shaucha (supreme contentment/purity)]
-
A.
virtue
Indicates that an entity possesses or exemplifies a morally good quality, trait, or behavior.
-
B.
vowedVirtue
Indicates that an entity has formally promised or committed to uphold a particular virtue or moral quality.
-
C.
virtuePraisedFor
Indicates that a particular virtue is being commended, admired, or spoken of approvingly by someone.
-
D.
virtuePromoted
Indicates that one entity actively encourages, supports, or increases the presence or practice of a particular virtue in another entity or context.
-
E.
virtueCategory
chosen
Indicates that something is classified as belonging to a particular category or type of virtue.
- 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:51 a.m.