Triple
T18440096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cboe EDGX Exchange |
E450502
|
entity |
| Predicate | hasFeeSchedule |
P25908
|
FINISHED |
| Object | published exchange fee schedule |
—
|
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: published exchange fee schedule | Statement: [Cboe EDGX Exchange, hasFeeSchedule, published exchange fee schedule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFeeSchedule Context triple: [Cboe EDGX Exchange, hasFeeSchedule, published exchange fee schedule]
-
A.
chargesFeeFor
Indicates that one entity requires payment of a fee from another entity in exchange for a specific service, product, or privilege.
-
B.
hasCharge
Indicates that an entity possesses a specific electrical or formal charge, such as positive, negative, or neutral.
-
C.
isFeePaying
Indicates that an entity is required to pay a fee in order to participate in, access, or receive a specified service, resource, or activity.
-
D.
feePolicy
chosen
Indicates the rules or conditions that determine how fees are calculated, applied, or charged in a given context.
-
E.
hasScheduleType
Indicates that an entity is associated with a particular kind or category of schedule (e.g., recurring, one-time, or specific scheduling pattern).
- 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.