Triple
T24922942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HUD-1 Settlement Statement |
E618774
|
entity |
| Predicate | requiredDeliveryTiming |
P39885
|
FINISHED |
| Object | at or before settlement |
—
|
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: at or before settlement | Statement: [HUD-1 Settlement Statement, requiredDeliveryTiming, at or before settlement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredDeliveryTiming Context triple: [HUD-1 Settlement Statement, requiredDeliveryTiming, at or before settlement]
-
A.
mustBeDeliveredBy
chosen
Indicates that one entity is required to be delivered or completed no later than a specified time, date, or deadline set by another entity.
-
B.
peakDeliveryTime
Indicates the time period during which deliveries are expected to be at their highest volume or frequency.
-
C.
deliveryGuarantee
Indicates that one party commits to ensuring that an item, service, or outcome will be delivered under specified conditions or within a defined timeframe.
-
D.
deliveryDate
Indicates the specific date on which a product, service, or item is scheduled or expected to be delivered.
-
E.
deliverySpeed
Indicates the rate or promptness with which an item, service, or information is delivered from a source to a recipient.
- 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_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 18, 2026, 5:29 a.m.