Triple
T8443917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parkmerced |
E199620
|
entity |
| Predicate | housingTenure |
P40076
|
FINISHED |
| Object | predominantly 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: predominantly rental units | Statement: [Parkmerced, housingTenure, predominantly rental units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: housingTenure Context triple: [Parkmerced, housingTenure, predominantly rental units]
-
A.
residenceType
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
B.
ownerOccupation
Indicates that the occupation or job role of an entity that owns something is being specified or described.
-
C.
housingPattern
chosen
Indicates the typical arrangement or distribution of housing units or residential structures within a given area or context.
-
D.
residenceStatus
Indicates the type or condition of an entity’s living arrangement or place of residence in relation to a specified location.
-
E.
residenceUsedFor
Indicates that a particular residence is used for a specific purpose, function, or activity.
- 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_69ca83170f9081909cd98f55614c6476 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe3122cfc8190ac6103fa4e4a7c45 |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0f5a3648190beb53a139a2d5482 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:09 p.m.