Triple
T13683643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York State Mitchell-Lama Housing Program |
E328062
|
entity |
| Predicate | hasHousingTenureType |
P105495
|
FINISHED |
| Object | rental |
—
|
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: rental | Statement: [New York State Mitchell-Lama Housing Program, hasHousingTenureType, rental]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHousingTenureType Context triple: [New York State Mitchell-Lama Housing Program, hasHousingTenureType, rental]
-
A.
hasHousingArrangement
chosen
Indicates that an entity has a specific type or status of housing or living arrangement in relation to another entity or context.
-
B.
hasHousingAccess
Indicates that an entity has the ability, right, or opportunity to obtain or use suitable housing.
-
C.
residenceType
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
D.
hasHouseholdType
Indicates the type or category of household associated with an entity (e.g., family, single-person, shared, etc.).
-
E.
residenceStatus
Indicates the type or condition of an entity’s living arrangement or place of residence in relation to a specified location.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc66e75188190a9e82fdc5eb26513 |
completed | April 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.