Triple
T18834482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nic |
E460621
|
entity |
| Predicate | familyLifeDisruptedBy |
P108983
|
FINISHED |
| Object | arrival of sperm-donor father |
—
|
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: arrival of sperm-donor father | Statement: [Nic, familyLifeDisruptedBy, arrival of sperm-donor father]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyLifeDisruptedBy Context triple: [Nic, familyLifeDisruptedBy, arrival of sperm-donor father]
-
A.
impactOnFamily
chosen
Indicates the effect or influence that something has on a family’s situation, dynamics, or well-being.
-
B.
familyLossEvent
Indicates an event in which a person experiences the loss or death of a family member.
-
C.
familyAspect
Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect in relation to another entity.
-
D.
familyDivision
Indicates a relationship where a family is split into distinct parts or groups, often due to conflict, separation, or differing affiliations.
-
E.
family
Indicates a familial relationship or connection between entities, such as being related by blood, marriage, or adoption.
- 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a99c1394819095c62eef040e552c |
completed | April 20, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.