Triple
T32130065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kim Kelly |
E820616
|
entity |
| Predicate | fromFamilyBackground |
P107737
|
FINISHED |
| Object | troubled home |
—
|
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: troubled home | Statement: [Kim Kelly, fromFamilyBackground, troubled home]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fromFamilyBackground Context triple: [Kim Kelly, fromFamilyBackground, troubled home]
-
A.
hasFamilyBackgroundIn
Indicates that an entity comes from, or is associated with, a particular familial or ancestral background.
-
B.
familyBackgroundDetail
chosen
Indicates detailed information about an entity’s family background, such as lineage, upbringing, or familial circumstances.
-
C.
loveInterestFamilyBackground
Indicates that information is being provided about the family background of a person's romantic partner or love interest.
-
D.
religiousFamilyBackground
Indicates that two entities are related through a shared or specified religious family upbringing or heritage.
-
E.
basedOnHisFamily
Indicates that something is determined, influenced, or justified by a particular male individual's family background, characteristics, or circumstances.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b96f3f108190a138524eb7e07fbf |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:29 a.m.