Triple
T32044079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hilltop, Minnesota |
E818290
|
entity |
| Predicate | hasPredominantHousingTenure |
P105495
|
FINISHED |
| Object | renter-occupied |
—
|
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: renter-occupied | Statement: [Hilltop, Minnesota, hasPredominantHousingTenure, renter-occupied]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPredominantHousingTenure Context triple: [Hilltop, Minnesota, hasPredominantHousingTenure, renter-occupied]
-
A.
isPrimarilyOwnerOccupiedHousing
Indicates that the housing unit is mainly used as a primary residence by its owner rather than being rented out or vacant.
-
B.
hasHousingArrangement
chosen
Indicates that an entity has a specific type or status of housing or living arrangement in relation to another entity or context.
-
C.
hasHousingAccess
Indicates that an entity has the ability, right, or opportunity to obtain or use suitable housing.
-
D.
homeOwnershipStatus
Indicates the type or condition of a person's or household's ownership of their place of residence.
-
E.
isPublicHousing
Indicates that the entity is designated as government-provided or subsidized residential housing intended for public use.
- 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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00a2f0d1588190a936ea7df0ef0464 |
completed | May 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_6a00a28ccd94819085b5e123f5a4769e |
completed | May 10, 2026, 3:21 p.m. |
Created at: May 1, 2026, 12:19 a.m.