Triple
T35653411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CFC |
E1030214
|
entity |
| Predicate | associatedWithFinancialInstrument |
P67141
|
FINISHED |
| Object | adjustable-rate mortgages |
—
|
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: adjustable-rate mortgages | Statement: [CFC, associatedWithFinancialInstrument, adjustable-rate mortgages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFinancialInstrument Context triple: [CFC, associatedWithFinancialInstrument, adjustable-rate mortgages]
-
A.
usesFinancialInstrument
Indicates that an entity employs or makes use of a particular financial instrument in performing an action or engaging in a transaction.
-
B.
hasFinancialInstrumentType
chosen
Indicates that an entity is associated with, or classified by, a specific type or category of financial instrument.
-
C.
associatedWithTicker
Indicates that an entity is linked or connected to a specific stock market ticker symbol.
-
D.
linkedInstrument
Indicates that one entity is associated with or connected to another as a related or corresponding instrument.
-
E.
associatedWithExchange
Indicates a relationship in which an entity is linked or connected to a particular exchange or trading platform.
- 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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.