Triple
T22675107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Term Asset-Backed Securities Loan Facility |
E560324
|
entity |
| Predicate | supportedInstrumentType |
P61314
|
FINISHED |
| Object | asset-backed securities |
—
|
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: asset-backed securities | Statement: [Term Asset-Backed Securities Loan Facility, supportedInstrumentType, asset-backed securities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedInstrumentType Context triple: [Term Asset-Backed Securities Loan Facility, supportedInstrumentType, asset-backed securities]
-
A.
supportedInstrument
chosen
Indicates that an entity provides compatibility with, or operational support for, a specified instrument.
-
B.
supportsInstrument
Indicates that one entity provides assistance, resources, or functionality that enables another entity (the instrument) to operate or be used effectively.
-
C.
allowedInstrument
Indicates that a particular instrument is permitted or authorized for use in a given context or activity.
-
D.
supportedEquipment
Indicates that one entity provides compatibility with, or operational support for, a specified piece of equipment.
-
E.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17823bd1881908958b0a8ba59e199 |
completed | April 29, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:11 p.m.