Triple
T24922930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HUD-1 Settlement Statement |
E618774
|
entity |
| Predicate | supersededByRegime |
P101
|
FINISHED |
| Object | TILA-RESPA Integrated Disclosure rule |
—
|
NE NERFINISHED |
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: TILA-RESPA Integrated Disclosure rule | Statement: [HUD-1 Settlement Statement, supersededByRegime, TILA-RESPA Integrated Disclosure rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supersededByRegime Context triple: [HUD-1 Settlement Statement, supersededByRegime, TILA-RESPA Integrated Disclosure rule]
-
A.
replacedRegime
Indicates that one regime has been supplanted and taken over by another regime.
-
B.
previouslyReplacedRegime
Indicates that one regime had earlier been replaced by another regime in the past.
-
C.
replacesRegime
Indicates that one governing regime is superseded and taken over by another.
-
D.
replacedRegimeOf
Indicates that one regime has taken the place of or succeeded another regime in power or authority.
-
E.
wasSupersededBy
chosen
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
- 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_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 18, 2026, 5:29 a.m.