Triple
T24057545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maggie Hardin |
E595848
|
entity |
| Predicate | donorForPlannedChild |
P88517
|
FINISHED |
| Object | Guy Childers |
—
|
NE NERFINISHED |
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: Guy Childers | Statement: [Maggie Hardin, donorForPlannedChild, Guy Childers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: donorForPlannedChild Context triple: [Maggie Hardin, donorForPlannedChild, Guy Childers]
-
A.
providedSpermDonorFor
chosen
Indicates that one entity served as the sperm donor used for another entity’s conception or reproductive process.
-
B.
adoptiveParent
Indicates that one entity is the legally recognized parent of another through adoption rather than biological descent.
-
C.
givenInAdoptionBy
Indicates that an entity was transferred into adoption through the action or decision of a specific giver (such as a person or organization).
-
D.
isDonorProgramOf
Indicates that one entity is a donor program that provides funding or resources to support another entity.
-
E.
adoptiveChild
Indicates that one entity is the child of another through legal adoption rather than biological descent.
- 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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da50d6108190a36bffaa475c8b93 |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:35 p.m.