Triple
T33113231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ben Cash |
E847384
|
entity |
| Predicate | raisesChildrenIn |
P175590
|
FINISHED |
| Object | isolation from modern society |
—
|
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: isolation from modern society | Statement: [Ben Cash, raisesChildrenIn, isolation from modern society]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raisesChildrenIn Context triple: [Ben Cash, raisesChildrenIn, isolation from modern society]
-
A.
asksChildrenTo
Indicates that one entity requests or directs children to perform an action or respond in some way.
-
B.
childrenWith
Indicates that two or more entities share one or more children together as parents or guardians.
-
C.
includedChildren
Indicates that certain child entities are contained within, or form part of, a specified parent entity.
-
D.
raisedAs
Indicates that one entity was brought up, nurtured, or reared in the role, identity, or condition specified by another entity.
-
E.
raisesAsOwnChildren
Indicates that one entity brings up and cares for another entity as if they were their own biological children.
- F. None of above. chosen
Provenance (4 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6ec34a481908851cd68697cb88c |
completed | May 3, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d30b9e048190b0982e30b7fdfa3c |
completed | May 3, 2026, 4:46 a.m. |
Created at: May 1, 2026, 1:27 a.m.