Triple
T36195772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bear Blu Jarecki |
E1047118
|
entity |
| Predicate | hasParentingStyleReportedByMother |
P38918
|
FINISHED |
| Object | attachment parenting |
—
|
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: attachment parenting | Statement: [Bear Blu Jarecki, hasParentingStyleReportedByMother, attachment parenting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentingStyleReportedByMother Context triple: [Bear Blu Jarecki, hasParentingStyleReportedByMother, attachment parenting]
-
A.
parentingStyle
chosen
Indicates the characteristic manner or approach an individual uses in raising, guiding, and disciplining a child.
-
B.
hasMotherDescribedAs
Indicates that an entity has a mother who is characterized or described in a specific way.
-
C.
parentingType
Indicates the specific style or approach used by a caregiver in raising or interacting with a child.
-
D.
hasParentalUnit
Indicates that an entity has a parent or guardian that serves as its primary caregiving or parental figure.
-
E.
hasDietReportedByMother
Indicates that information about an entity’s diet is provided or reported by the entity’s mother.
- 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_69f76e414bdc8190996f15a544220a3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffff262fac8190a26ed0577e1860bd |
completed | May 10, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69fffcad7d7c8190a4ad7bb35e33bb75 |
completed | May 10, 2026, 3:34 a.m. |
Created at: May 3, 2026, 4:08 p.m.