Triple

T24922935
Position Surface form Disambiguated ID Type / Status
Subject HUD-1 Settlement Statement E618774 entity
Predicate statusAfterTRID P159703 FINISHED
Object required only for certain transactions not covered by TRID 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: required only for certain transactions not covered by TRID | Statement: [HUD-1 Settlement Statement, statusAfterTRID, required only for certain transactions not covered by TRID]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: statusAfterTRID
Context triple: [HUD-1 Settlement Statement, statusAfterTRID, required only for certain transactions not covered by TRID]
  • A. legalStatusAfterEvent
    Indicates the legal condition or classification an entity has as a result of a specified event or occurrence.
  • B. statusTransmission
    Indicates that a status or state is being communicated or passed from one entity to another.
  • C. statusGrantedOn
    Indicates the date or time at which a particular status was officially conferred or became effective for an entity.
  • D. statusAfterRelocation
    Indicates the condition or state an entity has once it has been moved from its original location to a new one.
  • E. statusAfterUnification
    Indicates the resulting status or condition of an entity after a unification process or merging event has occurred.
  • 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_69e2fab9edd88190b86004a78a28bc20 completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f5f7a205688190b8f36bff5013247c completed May 2, 2026, 1:09 p.m.
PD Predicate disambiguation batch_69f5afd5baac8190bb8ed576813c8591 completed May 2, 2026, 8:03 a.m.
PDg Predicate description generation batch_69f5f6b32a8881909baa0db57b80d56a completed May 2, 2026, 1:05 p.m.
Created at: April 18, 2026, 5:29 a.m.