Triple
T37096063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vayu Kapoor Ahuja |
E918566
|
entity |
| Predicate | hasMaternalFamilyBackground |
P52719
|
FINISHED |
| Object | Kapoor film family |
E2191865
|
NE 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: Kapoor film family | Statement: [Vayu Kapoor Ahuja, hasMaternalFamilyBackground, Kapoor film family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaternalFamilyBackground Context triple: [Vayu Kapoor Ahuja, hasMaternalFamilyBackground, Kapoor film family]
-
A.
hasFamilyBackgroundIn
Indicates that an entity comes from, or is associated with, a particular familial or ancestral background.
-
B.
hasMaternalGrandmother
Indicates that an entity has a specific individual who is its mother’s mother.
-
C.
hasMotherOrigin
Indicates that an entity’s origin, source, or lineage is derived from or attributed to a mother entity.
-
D.
maternalAncestorOf
Indicates that one entity is an ancestor of another specifically through a chain of maternal (mother-to-child) relationships.
-
E.
maternalHouse
chosen
Indicates the house or family line associated with an entity’s mother, typically representing maternal ancestry or origin.
- F. None of above.
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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a036fb4650c81908df9b9ec8ed8594b |
completed | May 12, 2026, 6:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3efdd08da481909aa66f655cf0c6c3 |
completed | June 26, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_6a036f64dc648190a31cf944d3ea0f7d |
completed | May 12, 2026, 6:20 p.m. |
Created at: May 3, 2026, 4:14 p.m.