Triple
T20965289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | पाण्डु |
E516349
|
entity |
| Predicate | देवताओं से संबंध |
P60881
|
FINISHED |
| Object | देवपुत्र पाण्डवों के लौकिक पिता |
—
|
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: देवपुत्र पाण्डवों के लौकिक पिता | Statement: [पाण्डु, देवताओं से संबंध, देवपुत्र पाण्डवों के लौकिक पिता]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: देवताओं से संबंध Context triple: [पाण्डु, देवताओं से संबंध, देवपुत्र पाण्डवों के लौकिक पिता]
-
A.
relationshipToDeities
chosen
Indicates how an entity is connected or related to one or more deities, such as through worship, lineage, role, or status.
-
B.
relatedNameOfGod
Indicates that one entity is a name, title, or designation that refers to or is associated with God.
-
C.
sharesDeitiesWith
Indicates that two entities have one or more deities in common within their respective religious or mythological systems.
-
D.
associatedWithGod
Indicates a relationship in which an entity is linked, related, or connected in some meaningful way to a god or deity.
-
E.
intraVedicRelation
Indicates a relationship that connects elements within the Vedic corpus itself, such as links between Vedic texts, concepts, or traditions.
- 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb72ef4c8190bebdd2cef3c2148c |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:32 p.m.