Triple
T11864809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Support for Mortgage Interest |
E282253
|
entity |
| Predicate | introducedAsLoanFrom |
P67731
|
FINISHED |
| Object | April 2018 |
—
|
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: April 2018 | Statement: [Support for Mortgage Interest, introducedAsLoanFrom, April 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAsLoanFrom Context triple: [Support for Mortgage Interest, introducedAsLoanFrom, April 2018]
-
A.
loanedTo
Indicates that one entity has temporarily provided something it owns or controls to another entity with the expectation of its return.
-
B.
loanSource
chosen
Indicates that one entity is the origin or provider of a loan extended to another entity.
-
C.
introducedVia
Indicates that one entity was brought to the attention, presence, or awareness of another entity through a specific intermediary, method, or channel.
-
D.
areIntroducedBy
Indicates that one entity becomes known or presented to another entity through the action or mediation of a third party or process.
-
E.
hasLoanInfluenceFrom
Indicates that one entity’s loan terms, availability, or conditions are affected or shaped by 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a73883508190a78b5f4ba4a220df |
completed | April 10, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69d8a2589f0c8190ad82ff11acabae93 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.