Triple
T12309826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joad |
E293446
|
entity |
| Predicate | familyRoleInWork |
P45554
|
FINISHED |
| Object | central family of Dust Bowl migrants |
—
|
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: central family of Dust Bowl migrants | Statement: [Joad, familyRoleInWork, central family of Dust Bowl migrants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyRoleInWork Context triple: [Joad, familyRoleInWork, central family of Dust Bowl migrants]
-
A.
hasFamilyRelationInWork
chosen
Indicates that there exists a family relationship between two entities within the context of a specific work (e.g., book, film, or other creative work).
-
B.
hasFamilyRole
Indicates that one entity holds a specific familial role or position in relation to another entity.
-
C.
familyOrganizerRole
Indicates the specific role or capacity an individual holds as the organizer or manager within a family group or household.
-
D.
roleInSpouseCareer
Indicates the nature or extent of a person’s involvement or influence in their spouse’s professional career.
-
E.
householdRoleOfMother
Indicates the specific role or function that a mother holds within the household context.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec02c008190a56aae60a3d9eff6 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.