Triple
T15015911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DTCC |
E377958
|
entity |
| Predicate | handlesAssetClass |
P28209
|
FINISHED |
| Object | equities |
—
|
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: equities | Statement: [DTCC, handlesAssetClass, equities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesAssetClass Context triple: [DTCC, handlesAssetClass, equities]
-
A.
coversAssetClass
chosen
Indicates that one entity (such as a product, service, or policy) includes, applies to, or provides coverage for a specified asset class.
-
B.
overseesAssetClass
Indicates that one entity has responsibility for supervising, managing, or having authority over a particular asset class.
-
C.
replicatesAssetClass
Indicates that one financial instrument or entity is designed to mirror or track the performance and characteristics of a specified asset class.
-
D.
hasAsset
Indicates that one entity possesses, owns, or controls another entity as an asset.
-
E.
mainAssetManaged
Indicates that one entity is responsible for managing another entity that serves as the primary or main asset.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7623c3c819092ca36b358b01842 |
completed | April 15, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:55 a.m.