Triple
T26293753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mallory Hanson |
E661353
|
entity |
| Predicate | hasFamilyResponsibility |
P92492
|
FINISHED |
| Object | raising children |
—
|
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: raising children | Statement: [Mallory Hanson, hasFamilyResponsibility, raising children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyResponsibility Context triple: [Mallory Hanson, hasFamilyResponsibility, raising children]
-
A.
hasFamilyRole
Indicates that one entity holds a specific familial role or position in relation to another entity.
-
B.
hasFamilySituation
chosen
Indicates the familial status or circumstances that apply to an entity, such as their family composition, responsibilities, or living situation.
-
C.
hasFamilyHead
Indicates that one entity serves as the primary head or leader of another entity’s family unit.
-
D.
hasFamilyOrganization
Indicates that an entity is associated with, belongs to, or is structured within a particular family-based organizational unit or system.
-
E.
hasChildCare
Indicates that an entity provides, offers, or is associated with child care services or facilities for children.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 26, 2026, 10:10 p.m.