Triple
T31887792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mother and baby homes |
E814050
|
entity |
| Predicate | consequenceForMothers |
P132927
|
FINISHED |
| Object | loss of parental rights |
—
|
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: loss of parental rights | Statement: [mother and baby homes, consequenceForMothers, loss of parental rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consequenceForMothers Context triple: [mother and baby homes, consequenceForMothers, loss of parental rights]
-
A.
consequenceOfAbuse
Indicates that one situation, condition, or outcome occurs as a direct result of abusive behavior or treatment.
-
B.
consequenceOfChildlessness
Indicates a condition, event, or outcome that arises specifically as a result of being childless.
-
C.
maternalInfluence
Indicates the effect a mother or maternal figure has on shaping, guiding, or impacting another entity’s behavior, development, or state.
-
D.
consequenceOfInfluence
chosen
Indicates that one event, state, or condition occurs as a result of the influence or impact exerted by another.
-
E.
motherIn
Indicates that one entity is the mother of another entity within a specified context or domain.
- 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_69f348ef817481908440e2250319bcc8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 30, 2026, 11:57 p.m.