Triple
T6971389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saravanabhava |
E161605
|
entity |
| Predicate | birthNarrativeElement |
P16792
|
FINISHED |
| Object | born from sparks or semen of Shiva |
—
|
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: born from sparks or semen of Shiva | Statement: [Saravanabhava, birthNarrativeElement, born from sparks or semen of Shiva]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: birthNarrativeElement Context triple: [Saravanabhava, birthNarrativeElement, born from sparks or semen of Shiva]
-
A.
birthProcess
Indicates the biological process through which a new organism is brought into existence from its parent or parents.
-
B.
birthEvent
Indicates an event in which an entity comes into existence by being born, typically linking the newborn to contextual details such as time, place, and participants.
-
C.
birthType
chosen
Indicates the manner or method by which a birth occurred or was brought about.
-
D.
gaveBirthTo
Indicates that one entity is the biological parent who delivered another entity as offspring.
-
E.
gaveBirthAt
Indicates that one entity gave birth at a specific location or time associated with another entity.
- 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_69c68854a0d88190bc0bf82263f1afce |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db38013081908037d23843dccad7 |
completed | March 27, 2026, 7:32 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c262508190a7708b3d9cf23d7c |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:30 p.m.