Triple
T15243455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOFR |
E364315
|
entity |
| Predicate | referenceMarket |
P117743
|
FINISHED |
| Object | tri-party repo |
—
|
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: tri-party repo | Statement: [SOFR, referenceMarket, tri-party repo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referenceMarket Context triple: [SOFR, referenceMarket, tri-party repo]
-
A.
relatedMarket
Indicates that two markets are connected or associated, such that activity, conditions, or changes in one market are relevant to or influence the other.
-
B.
coreMarket
Indicates that an entity serves as the primary or most important market for another entity’s products, services, or activities.
-
C.
marketsIn
Indicates that one entity promotes, sells, or offers another entity’s products or services within a particular market or geographic area.
-
D.
coversMarket
Indicates that one entity operates in, serves, or has business presence within a particular market or geographic/sectoral area.
-
E.
marketSize
Indicates the total volume or value of demand for a product, service, or market segment within a defined scope (such as a time period or geographic region).
- 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.