Triple
T24852102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Natella Abashwili |
E621914
|
entity |
| Predicate | parentalBehavior |
P152889
|
FINISHED |
| Object | neglectful mother |
—
|
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: neglectful mother | Statement: [Natella Abashwili, parentalBehavior, neglectful mother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentalBehavior Context triple: [Natella Abashwili, parentalBehavior, neglectful mother]
-
A.
parentingStyle
Indicates the characteristic manner or approach an individual uses in raising, guiding, and disciplining a child.
-
B.
parentalCare
Indicates that one entity provides nurturing, protection, or support to another in a parent-like role.
-
C.
parentalCharacter
chosen
Indicates a relationship where one entity exhibits traits, behaviors, or qualities characteristic of a parent toward another entity.
-
D.
parentalIssue
Indicates that there is a problem, conflict, or difficulty involving a person's relationship or situation with their parent(s).
-
E.
parentInfluence
Indicates that one entity has a formative or guiding effect on another entity in the role of a parent.
- 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_69e2fac297e481909d3aedc75f585e42 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:20 a.m.