Triple
T19731063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sutasoma |
E473853
|
entity |
| Predicate | isUpapandava |
P137123
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sutasoma, isUpapandava, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUpapandava Context triple: [Sutasoma, isUpapandava, true]
-
A.
isPancharangaKshetram
Indicates that a temple or sacred site is recognized as one of the Pancharanga Kshetrams, the five traditional holy shrines dedicated to Lord Ranganatha (Vishnu) along the Kaveri river.
-
B.
sonWithIndra
Indicates a parent–child relationship where the child is a son associated with or born to Indra.
-
C.
inRamayana
Indicates that the subject participates in, appears within, or is otherwise part of the events or narrative of the Ramayana.
-
D.
yakshini
Indicates a mythological or spiritual association involving a yakshini, such as being protected by, devoted to, influenced by, or otherwise connected to this female nature spirit.
-
E.
VarunaIs
Indicates that an entity is identified as or associated with Varuna.
- 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e649fd18148190a6e85b2be0069dde |
completed | April 20, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:47 p.m.