Triple
T15243466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOFR |
E364315
|
entity |
| Predicate | compoundedVersionsUsedFor |
P117744
|
FINISHED |
| Object | term-adjusted interest calculations |
—
|
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: term-adjusted interest calculations | Statement: [SOFR, compoundedVersionsUsedFor, term-adjusted interest calculations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compoundedVersionsUsedFor Context triple: [SOFR, compoundedVersionsUsedFor, term-adjusted interest calculations]
-
A.
hasMultipleVersions
Indicates that an entity exists in more than one distinct version or revision.
-
B.
compactedVariantUsedFor
Indicates that one entity is a compacted or compressed version of another entity that is used in its place for some purpose.
-
C.
updatedWithEachVersionOf
Indicates that something is modified or revised every time a new version of another entity is released.
-
D.
compositeVersionDescription
Indicates a descriptive text that explains the content, purpose, or characteristics of a specific composite version.
-
E.
separateVersionsFor
Indicates that distinct versions must be maintained or handled separately for the related entities.
- F. None of above. chosen
Provenance (4 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007dcc33081908545ea1a1d2c19fe |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:13 a.m.