Triple
T17922052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICE Clear Credit LLC |
E448096
|
entity |
| Predicate | clearsInstrumentType |
P12711
|
FINISHED |
| Object | single-name credit default swaps |
—
|
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: single-name credit default swaps | Statement: [ICE Clear Credit LLC, clearsInstrumentType, single-name credit default swaps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clearsInstrumentType Context triple: [ICE Clear Credit LLC, clearsInstrumentType, single-name credit default swaps]
-
A.
typeOfInstrument
chosen
Indicates the specific kind or category of instrument associated with an entity.
-
B.
allowedInstrument
Indicates that a particular instrument is permitted or authorized for use in a given context or activity.
-
C.
musicInstrumentation
Indicates the specific instruments or instrumental forces used to perform a piece of music.
-
D.
alsoAppliesInstrument
Indicates that a condition, rule, or characteristic that applies to one instrument also applies to another instrument.
-
E.
parentInstrument
Indicates that one instrument serves as the broader, containing, or originating instrument from which another, more specific or derived instrument is related.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a30ad8748190b28d3e8b5afab2ef |
completed | April 19, 2026, 9:40 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:20 a.m.