Triple
T19266179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adhiratha |
E481784
|
entity |
| Predicate | treatsKarnaAs |
P135348
|
FINISHED |
| Object | biological son |
—
|
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: biological son | Statement: [Adhiratha, treatsKarnaAs, biological son]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatsKarnaAs Context triple: [Adhiratha, treatsKarnaAs, biological son]
-
A.
relationshipToKauravas
Indicates the type or nature of a person's familial or social relationship to the Kauravas.
-
B.
sonWithIndra
Indicates a parent–child relationship where the child is a son associated with or born to Indra.
-
C.
sonWithDharma
Indicates a parent–child relationship where the child is a son whose birth or status is in accordance with dharma (righteous or proper duty/law).
-
D.
treatsRightAs
Indicates that one entity provides medical or therapeutic treatment to another entity who is identified as the right-hand participant in the relationship.
-
E.
hasRatha
Indicates that one entity possesses, includes, or is associated with a chariot (ratha) as part of its attributes or composition.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8d58988190a942627b1fb79285 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4df51ac6c819091ce72b07790ffa6 |
completed | April 19, 2026, 1:57 p.m. |
Created at: April 10, 2026, 1:29 p.m.