Triple
T24914801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evelyn Harper |
E623950
|
entity |
| Predicate | relationshipWithCharlieHarper |
P153973
|
FINISHED |
| Object | strained mother-son relationship |
—
|
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: strained mother-son relationship | Statement: [Evelyn Harper, relationshipWithCharlieHarper, strained mother-son relationship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWithCharlieHarper Context triple: [Evelyn Harper, relationshipWithCharlieHarper, strained mother-son relationship]
-
A.
relationshipTypeWithCharlie Harper
chosen
Indicates the specific nature or category of relationship that an entity has with Charlie Harper.
-
B.
relationshipToHarveyCheyneJr
Indicates the specific familial, social, or professional relationship that an entity has to Harvey Cheyne Jr.
-
C.
familyRelationToCharltons
Indicates the type of familial relationship an entity has to the Charltons.
-
D.
relationshipWithJakeHarper
Indicates that one entity has some form of relationship or connection with Jake Harper.
-
E.
relationshipWithAlanHarper
Indicates that one entity has a specified type of personal or social relationship with Alan Harper.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 18, 2026, 5:28 a.m.