Triple
T18560690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ovambo people |
E453629
|
entity |
| Predicate | traditionalHouseholdStructure |
P39277
|
FINISHED |
| Object | extended family |
—
|
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: extended family | Statement: [Ovambo people, traditionalHouseholdStructure, extended family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalHouseholdStructure Context triple: [Ovambo people, traditionalHouseholdStructure, extended family]
-
A.
houseOrFamily
Indicates that two entities are related through a shared house, household, or family membership.
-
B.
familyType
chosen
Indicates the specific familial relationship or category that characterizes how the related entities are connected as family.
-
C.
householdStatus
Indicates the type or condition of a person’s living arrangement within a household, such as their role, membership, or current residency status.
-
D.
householdTypeAtNumber4
Indicates the type or classification of the household associated with entity number 4.
-
E.
domesticStructure
Indicates a structural or organizational relationship within a household or domestic setting, such as how roles, responsibilities, or living arrangements are arranged among its members.
- 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e538098a148190b0fc7098ce3c62fd |
completed | April 19, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:42 a.m.