Triple
T19266178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adhiratha |
E481784
|
entity |
| Predicate | parentalRelationshipToKarna |
P75214
|
FINISHED |
| Object | adoptive father |
—
|
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: adoptive father | Statement: [Adhiratha, parentalRelationshipToKarna, adoptive father]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentalRelationshipToKarna Context triple: [Adhiratha, parentalRelationshipToKarna, adoptive father]
-
A.
relationshipToKauravas
Indicates the type or nature of a person's familial or social relationship to the Kauravas.
-
B.
relationshipWithFather
Indicates a familial relationship that specifically connects an individual to their father.
-
C.
politicalRelationship
Indicates a relationship in which entities are connected through political roles, alliances, affiliations, or interactions within a political context.
-
D.
familyRelationInSomeTraditions
Indicates a family relationship that is recognized or defined specifically within certain cultural, religious, or regional traditions rather than universally.
-
E.
parentRelationship
chosen
Indicates a familial relationship in which one entity is the parent of 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_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. |
Created at: April 10, 2026, 1:29 p.m.