Triple
T20964613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kathaka |
E516333
|
entity |
| Predicate | hasMantraStyle |
P142274
|
FINISHED |
| Object | mixed prose and verse |
—
|
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: mixed prose and verse | Statement: [Kathaka, hasMantraStyle, mixed prose and verse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMantraStyle Context triple: [Kathaka, hasMantraStyle, mixed prose and verse]
-
A.
mantraText
Indicates that a mantra is associated with a specific textual content or wording.
-
B.
hasVerseStyle
Indicates that one entity is characterized by, or presented in, the verse style specified by another entity.
-
C.
possessedMantraFrom
Indicates that one entity had ownership or control of a particular mantra originating from another entity or source.
-
D.
hasLyricalStyle
Indicates that one entity possesses or is characterized by a particular lyrical style in relation to another entity or context.
-
E.
hasDevotionalFormula
Indicates a relationship where one entity includes, uses, or is associated with a specific devotional formula (such as a set religious phrase, prayer, or invocation).
- 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb71d644819087e00933fcc26217 |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:32 p.m.