Triple

T594278
Position Surface form Disambiguated ID Type / Status
Subject CME E17344 entity
Predicate clearingServices P5407 FINISHED
Object central counterparty clearing 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: central counterparty clearing | Statement: [CME, clearingServices, central counterparty clearing]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: clearingServices
Context triple: [CME, clearingServices, central counterparty clearing]
  • A. clearingHouse chosen
    Indicates that an entity functions as an intermediary organization that receives, processes, and redistributes transactions, information, or obligations between other parties.
  • B. serviceOf
    Indicates that one entity performs, provides, or fulfills a function or duty on behalf of another entity.
  • C. cleanupContractor
    Indicates that an entity serves as the contractor responsible for performing cleanup activities for another entity or project.
  • D. coordinatesTransportationServicesWith
    Indicates that one entity organizes and manages the alignment and collaboration of transportation services with another entity or set of entities.
  • E. service
    Indicates that one entity performs work, assistance, or functions to meet the needs or requests of another entity.
  • 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_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.
Created at: March 1, 2026, 7:33 p.m.