Triple
T25458719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cboe Clear Europe |
E637983
|
entity |
| Predicate | tradingVenueCoverage |
P158196
|
FINISHED |
| Object | Cboe Europe |
—
|
NE NERFINISHED |
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: Cboe Europe | Statement: [Cboe Clear Europe, tradingVenueCoverage, Cboe Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradingVenueCoverage Context triple: [Cboe Clear Europe, tradingVenueCoverage, Cboe Europe]
-
A.
identifiesTradingVenue
chosen
Indicates that one entity specifies or designates the trading venue associated with another entity or transaction.
-
B.
marketCovered
Indicates that one entity’s products or services are already available or served within the geographic or customer market associated with another entity.
-
C.
hasTradingVenueType
Indicates the specific category or type of trading venue associated with a given trading platform or marketplace.
-
D.
hasTradingVenueCode
Indicates that an entity is associated with a specific trading venue through its designated code.
-
E.
stockExchangeExposure
Indicates the degree to which an entity is financially affected by, or sensitive to, movements and conditions in stock exchanges.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 21, 2026, 2:11 p.m.