Triple
T13858054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HomeReady mortgage program |
E333114
|
entity |
| Predicate | propertyTypeEligible |
P24942
|
FINISHED |
| Object | single-family homes |
—
|
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: single-family homes | Statement: [HomeReady mortgage program, propertyTypeEligible, single-family homes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyTypeEligible Context triple: [HomeReady mortgage program, propertyTypeEligible, single-family homes]
-
A.
eligibleProperties
chosen
Indicates that certain properties meet the required conditions or criteria to qualify for a specified purpose or status.
-
B.
propertyTypeOwned
Indicates that one entity owns a specific type or category of property in relation to another entity.
-
C.
residenceType
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
D.
collateralType
Indicates the kind or category of collateral associated with an obligation, agreement, or financial exposure.
-
E.
propertyType_rid
Indicates that an entity is associated with a specific property type identified by a unique resource identifier (RID).
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02dc9f488190b7181dcb7e304632 |
completed | April 14, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:14 p.m.