Triple
T594297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CME |
E17344
|
entity |
| Predicate | scopeOfProducts |
P16090
|
FINISHED |
| Object | financial derivatives |
—
|
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: financial derivatives | Statement: [CME, scopeOfProducts, financial derivatives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeOfProducts Context triple: [CME, scopeOfProducts, financial derivatives]
-
A.
scopeOfUse
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
-
B.
scopeOfContribution
Indicates the specific area, domain, or extent within which an entity’s contribution or involvement applies.
-
C.
scopeDetail
Indicates a more specific or refined characterization of the extent, boundaries, or coverage of something within a broader scope.
-
D.
operationalScope
Indicates the range, extent, or boundaries within which an entity, process, or activity is authorized or designed to operate.
-
E.
brandingScope
Indicates the extent or range within which a particular brand identity, strategy, or elements are applied or recognized.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bd15c5881909b59ed4c88687e7b |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494cd7d3c8190af008acf34a2293b |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985ada988190aaea628a9b55bca4 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:33 p.m.