Triple
T37096064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vayu Kapoor Ahuja |
E918566
|
entity |
| Predicate | hasPaternalFamilyBackground |
P13742
|
FINISHED |
| Object | business family |
—
|
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: business family | Statement: [Vayu Kapoor Ahuja, hasPaternalFamilyBackground, business family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPaternalFamilyBackground Context triple: [Vayu Kapoor Ahuja, hasPaternalFamilyBackground, business family]
-
A.
hasFamilyBackgroundIn
chosen
Indicates that an entity comes from, or is associated with, a particular familial or ancestral background.
-
B.
hasPaternalGrandparent
Indicates that one entity is the paternal grandparent (father’s parent) of another entity.
-
C.
paternalHouse
Indicates the family house or lineage associated with a person's father.
-
D.
hasTraditionalFather
Indicates that an entity has a father in the traditional biological or socially recognized paternal sense.
-
E.
hasPatrilinealOrigin
Indicates that something originates from or is derived through the male (father’s) ancestral line.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a0039c2d5d48190b8ef2c7ef17d8dc5 |
completed | May 10, 2026, 7:54 a.m. |
| PD | Predicate disambiguation | batch_6a0038e525448190a4c815f51595e78d |
completed | May 10, 2026, 7:51 a.m. |
Created at: May 3, 2026, 4:14 p.m.