Triple
T31598037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perry Wright |
E806271
|
entity |
| Predicate | parentOfAbusiveChild |
P188104
|
FINISHED |
| Object | Max Wright |
—
|
NE NERFINISHED |
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: Max Wright | Statement: [Perry Wright, parentOfAbusiveChild, Max Wright]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentOfAbusiveChild Context triple: [Perry Wright, parentOfAbusiveChild, Max Wright]
-
A.
hasAbusiveParent
Indicates that an individual has a parent who behaves in an abusive, harmful, or mistreating manner toward them.
-
B.
parentalIssue
Indicates that there is a problem, conflict, or difficulty involving a person's relationship or situation with their parent(s).
-
C.
victimOfInjusticeInFamily
Indicates that one entity has suffered unfair or wrongful treatment within the context of their family relationships or family environment.
-
D.
typeOfAbuse
Indicates the specific kind or category of abusive behavior that one entity inflicts on another.
-
E.
familyAuthority
Indicates that one entity holds recognized decision-making power or control over another within a family or household context.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fba28684208190921694f23e350c3b |
completed | May 6, 2026, 8:20 p.m. |
Created at: April 30, 2026, 10:31 p.m.