Triple
T38051225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louis Connelly |
E949763
|
entity |
| Predicate | separationFromChildReason |
P138190
|
FINISHED |
| Object | unaware of child’s existence |
—
|
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: unaware of child’s existence | Statement: [Louis Connelly, separationFromChildReason, unaware of child’s existence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separationFromChildReason Context triple: [Louis Connelly, separationFromChildReason, unaware of child’s existence]
-
A.
causesSeparationFrom
Indicates that one entity brings about or is responsible for another entity becoming separated from a third entity or context.
-
B.
createdBySeparationFrom
Indicates that one entity comes into existence as a result of being separated or split off from another entity.
-
C.
reasonForDisownment
chosen
Indicates the specific cause or justification for which one party disowns or severs familial or formal ties with another.
-
D.
separationAttributedTo
Indicates that a separation or split between entities is explained as being caused by a specified factor, event, or agent.
-
E.
laterSeparatedFrom
Indicates that one entity became separated from another at a later time than some referenced separation event.
- 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_69f76f000cf081908c11fb5443b392e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.