Triple
T18440075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cboe EDGX Exchange |
E450502
|
entity |
| Predicate | hasPricingFeature |
P18395
|
FINISHED |
| Object | competitive pricing structure |
—
|
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: competitive pricing structure | Statement: [Cboe EDGX Exchange, hasPricingFeature, competitive pricing structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPricingFeature Context triple: [Cboe EDGX Exchange, hasPricingFeature, competitive pricing structure]
-
A.
isValuePriced
Indicates that something is offered at a relatively low or favorable price compared to typical or premium alternatives.
-
B.
hasPriceUnit
Indicates that a price value is expressed in a specific unit of currency or measurement.
-
C.
productPricing
Indicates the pricing details or cost structure assigned to a specific product.
-
D.
pricingCharacteristic
chosen
Indicates how the price of something is determined, structured, or behaves (e.g., fixed, variable, discounted, tiered).
-
E.
offersPricingModel
Indicates that one entity provides or makes available a specific pricing model to another entity or for a particular offering.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c0fda908190901a108fb9982a2d |
completed | April 19, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:30 a.m.