Triple
T24922944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HUD-1 Settlement Statement |
E618774
|
entity |
| Predicate | relatedDocumentAbbreviation |
P144194
|
FINISHED |
| Object | GFE |
—
|
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: GFE | Statement: [HUD-1 Settlement Statement, relatedDocumentAbbreviation, GFE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedDocumentAbbreviation Context triple: [HUD-1 Settlement Statement, relatedDocumentAbbreviation, GFE]
-
A.
relatedAbbreviationSystem
Indicates that one entity is associated with, or belongs to, a particular system of abbreviations used to represent it.
-
B.
alternativeAbbreviation
chosen
Indicates that one term serves as an alternative shortened form or acronym for another term.
-
C.
legalCitationAbbreviation
Indicates that one legal citation is an abbreviated or shortened form of another legal citation.
-
D.
abbreviationOrShortForm
Indicates that one term is an abbreviation or shortened form of another term.
-
E.
relatedOrganizationAbbreviation
Indicates that one organization is associated with another through a specific abbreviated form of its name or title.
- 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 18, 2026, 5:29 a.m.