Triple
T31887794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mother and baby homes |
E814050
|
entity |
| Predicate | consequenceForChildren |
P812
|
FINISHED |
| Object | identity loss |
—
|
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: identity loss | Statement: [mother and baby homes, consequenceForChildren, identity loss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consequenceForChildren Context triple: [mother and baby homes, consequenceForChildren, identity loss]
-
A.
childRestorationConsequence
Indicates the outcome or effect that results from restoring a child entity to a previous or original state.
-
B.
consequenceOfInfluence
Indicates that one event, state, or condition occurs as a result of the influence or impact exerted by another.
-
C.
consequenceOfChildlessness
Indicates a condition, event, or outcome that arises specifically as a result of being childless.
-
D.
hasConsequence
chosen
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
-
E.
consequenceOfRemarriage
Indicates that a particular outcome, status change, or legal effect occurs as a direct result of someone remarrying.
- 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_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 30, 2026, 11:57 p.m.