Triple
T3031880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Home Mortgage Disclosure Act |
E82914
|
entity |
| Predicate | dataFieldsInclude |
P28893
|
FINISHED |
| Object | loan amount |
—
|
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: loan amount | Statement: [Home Mortgage Disclosure Act, dataFieldsInclude, loan amount]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataFieldsInclude Context triple: [Home Mortgage Disclosure Act, dataFieldsInclude, loan amount]
-
A.
hasDataFields
chosen
Indicates that an entity possesses or is associated with specific data fields or attributes.
-
B.
collectingField
Indicates that one entity serves as the field or location where another entity gathers, accumulates, or collects items, data, or resources.
-
C.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
D.
supportsField
Indicates that one entity provides the necessary structure, stability, or backing for a particular field, area, or domain associated with another entity.
-
E.
dataTypes
Indicates that one entity specifies or defines the kinds or formats of data that are valid or expected for another entity.
- 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_69ad8b21a62881908ec5dd4fba4a187c |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9aefc2dc8190ad9b349ca45b7e30 |
completed | March 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ad961e2a408190afb1759132701305 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.