Triple
T29492332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Divya Saasha |
E748113
|
entity |
| Predicate | parentalFameContext |
P70678
|
FINISHED |
| Object | child of a leading Tamil cinema actor |
—
|
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: child of a leading Tamil cinema actor | Statement: [Divya Saasha, parentalFameContext, child of a leading Tamil cinema actor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentalFameContext Context triple: [Divya Saasha, parentalFameContext, child of a leading Tamil cinema actor]
-
A.
familyContext
Indicates that the entities are related or associated within a family or household context, such as kinship, caregiving, or shared domestic life.
-
B.
bearerFamilySocialContext
chosen
Indicates the social and familial circumstances or environment surrounding the bearer in relation to others.
-
C.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
D.
parentInfluence
Indicates that one entity has a formative or guiding effect on another entity in the role of a parent.
-
E.
parentalCare
Indicates that one entity provides nurturing, protection, or support to another in a parent-like role.
- 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_69f0bd448c6881908aa6b475cefd5ddc |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 28, 2026, 4:15 p.m.