Triple
T15835946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Home Affordable Modification Program |
E383983
|
entity |
| Predicate | endOfNewApplications |
P48547
|
FINISHED |
| Object | December 31, 2016 |
—
|
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: December 31, 2016 | Statement: [Home Affordable Modification Program, endOfNewApplications, December 31, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfNewApplications Context triple: [Home Affordable Modification Program, endOfNewApplications, December 31, 2016]
-
A.
exampleApplication
Indicates that something serves as a representative or illustrative instance of how an application is used or functions.
-
B.
fullyAppliedTo
Indicates that an action, function, or process has been completely and exhaustively applied to a target entity, with no remaining parameters or partial application.
-
C.
endOf
chosen
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
-
D.
deploymentEnd
Indicates the point in time or event at which a deployment process or deployment state comes to an end.
-
E.
applicationProcessedBy
Indicates that an application has been handled or dealt with by a particular agent or system.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e0e1cc8190851b30b03cf9c9b8 |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.