Triple
T263551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Home Equity Conversion Mortgage program |
E5804
|
entity |
| Predicate | loanType |
P9377
|
FINISHED |
| Object | reverse mortgage |
—
|
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: reverse mortgage | Statement: [Home Equity Conversion Mortgage program, loanType, reverse mortgage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loanType Context triple: [Home Equity Conversion Mortgage program, loanType, reverse mortgage]
-
A.
typeOfContract
Indicates the specific kind or category of contractual agreement that applies between the related entities.
-
B.
settlementType
Indicates the specific kind or category of human settlement an entity represents, such as a city, village, town, or hamlet.
-
C.
obligationType
Indicates the specific kind or category of duty, requirement, or commitment that applies within an obligation relationship.
-
D.
residenceType
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
E.
eligibleBorrower
Indicates that an entity meets the required conditions to be allowed to borrow (e.g., money, items, or resources) under a given set of rules or policies.
- F. None of above. chosen
Provenance (4 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_69a258dd8ea08190ac554a1cc8dfd8c3 |
completed | Feb. 28, 2026, 2:54 a.m. |
| NER | Named-entity recognition | batch_69a25d8e809881908a58c9a4e3ba07c3 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b6e07748190834022a65ba6d803 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25d0ec71081908478c800be4f7bb0 |
completed | Feb. 28, 2026, 3:12 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.