Triple
T35653394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CFC |
E1030214
|
entity |
| Predicate | associatedRiskType |
P15871
|
FINISHED |
| Object | subprime 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: subprime mortgages | Statement: [CFC, associatedRiskType, subprime mortgages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRiskType Context triple: [CFC, associatedRiskType, subprime mortgages]
-
A.
riskType
chosen
Indicates the category or nature of risk associated with an entity, event, or relationship.
-
B.
hasRiskFor
Indicates that one entity is susceptible or exposed to the possibility of experiencing a harmful event, condition, or outcome associated with another entity.
-
C.
hasRiskFrom
Indicates that one entity is exposed to or may suffer potential harm, loss, or adverse effects as a result of another entity.
-
D.
riskListedBy
Indicates that a risk has been documented, identified, or cataloged by a particular agent or source.
-
E.
riskElement
Indicates that one entity is a risk-related component, factor, or contributor associated with another entity within a risk context.
- 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.