Triple
T15511066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CME Globex |
E368708
|
entity |
| Predicate | timeInForceOptions |
P71724
|
FINISHED |
| Object | day orders |
—
|
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: day orders | Statement: [CME Globex, timeInForceOptions, day orders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInForceOptions Context triple: [CME Globex, timeInForceOptions, day orders]
-
A.
timeOfExecutions
Indicates the specific time or times at which one or more executions (such as tasks, processes, or actions) occur.
-
B.
tradingHoursType
Indicates the classification of an entity’s trading hours, such as whether they are regular, extended, holiday-specific, or of another defined type.
-
C.
timeFrameSpecified
Indicates that a specific temporal period or duration has been explicitly defined or constrained for the related event, action, or relationship.
-
D.
hasTimeOptions
chosen
Indicates that an entity is associated with one or more selectable time choices or configurations.
-
E.
settlementPeriod
Indicates the length of time between a transaction or agreement and its final settlement or completion.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e04030c0208190a1931ea130075603 |
completed | April 16, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:55 a.m.