Triple
T6027007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Terrace |
E134204
|
entity |
| Predicate | hasHousingTenure |
P542
|
FINISHED |
| Object | mix of owner-occupied and rental units |
—
|
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 owner-occupied and rental units | Statement: [River Terrace, hasHousingTenure, mix of owner-occupied and rental units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHousingTenure Context triple: [River Terrace, hasHousingTenure, mix of owner-occupied and rental units]
-
A.
hasHousingAccess
Indicates that an entity has the ability, right, or opportunity to obtain or use suitable housing.
-
B.
hasPublicHousing
Indicates that a location or jurisdiction provides or contains government-funded residential housing available to the public.
-
C.
hasHouse
Indicates that one entity possesses, owns, or is provided with a house in relation to another entity.
-
D.
hasPublicHousingAuthority
Indicates that an entity is associated with, governed by, or served by a specific public housing authority.
-
E.
residenceType
chosen
Indicates the kind or category of dwelling or living arrangement associated with an entity.
- 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_69c0087515148190a97475d412563865 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0560cdc308190b25ca8ecb42c4e4f |
completed | March 22, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69c049e75b3881908be106fbcf8c68d4 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:07 p.m.