Triple
T18451058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gandhari |
E450781
|
entity |
| Predicate | relationshipToPandavas |
P38921
|
FINISHED |
| Object | paternal aunt by marriage |
—
|
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: paternal aunt by marriage | Statement: [Gandhari, relationshipToPandavas, paternal aunt by marriage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToPandavas Context triple: [Gandhari, relationshipToPandavas, paternal aunt by marriage]
-
A.
relationshipToCharacter
chosen
Indicates the specific type of personal, social, or narrative connection that one entity has to a given character.
-
B.
playerRelations
Indicates the nature or status of the relationship between players, such as alliances, rivalries, or other interpersonal dynamics.
-
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.
relationshipToMahāpajāpatīGotamī
Indicates the specific familial or relational connection an entity has to Mahāpajāpatī Gotamī.
-
E.
characterActorRelationship
Indicates a relationship where an actor portrays or is associated with a specific character in a work.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52648476c8190a5d8c3297d836f62 |
completed | April 19, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:31 a.m.