Triple
T18502294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cboe EDGA Exchange |
E452105
|
entity |
| Predicate | tradingSession |
P30924
|
FINISHED |
| Object | regular trading hours |
—
|
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: regular trading hours | Statement: [Cboe EDGA Exchange, tradingSession, regular trading hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradingSession Context triple: [Cboe EDGA Exchange, tradingSession, regular trading hours]
-
A.
hasTradingSession
chosen
Indicates that an entity participates in or is associated with a specific trading session or period during which trading activities occur.
-
B.
tradingSegment
Indicates that one entity operates within, or is associated with, a specific trading segment or market subdivision for transactional activities.
-
C.
actualTrading
Indicates the occurrence of real, executed trading activity between parties, as opposed to planned, simulated, or potential trades.
-
D.
tradingStatus
Indicates the current state or condition of an entity’s ability to be traded or engaged in trading activities.
-
E.
tradesDuring
Indicates that a trading activity or transaction occurs within a specified time period or during a particular event or session.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e532c535908190bdc90c58fc5bdaf7 |
completed | April 19, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.