Triple
T2069415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lone Tree, Iowa |
E45980
|
entity |
| Predicate | hasHouseholdType |
P35173
|
FINISHED |
| Object | mix of family and non-family households |
—
|
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: mix of family and non-family households | Statement: [Lone Tree, Iowa, hasHouseholdType, mix of family and non-family households]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHouseholdType Context triple: [Lone Tree, Iowa, hasHouseholdType, mix of family and non-family households]
-
A.
hasParentHouse
Indicates that an entity is associated with or belongs to a specific parent house within a hierarchical or familial structure.
-
B.
hasHouse
Indicates that one entity possesses, owns, or is provided with a house in relation to another entity.
-
C.
hasFamilyHead
Indicates that one entity serves as the primary head or leader of another entity’s family unit.
-
D.
hasGeneralHouse
Indicates that an entity possesses or is associated with a general-purpose house or primary residential building.
-
E.
hasMainBreadwinner
Indicates that one entity serves as the primary income earner or financial provider for another entity (such as a household or family).
- F. None of above. chosen
Provenance (4 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_69a8891b38288190abd572ccad9b6928 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9f51a008190aead0173a9289204 |
completed | March 7, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69abb7aee9b48190999620176e3a6ee2 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb87b9fc08190a748c278ef2d7dc7 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:41 p.m.