Triple
T32061307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago |
E818754
|
entity |
| Predicate | hasFuturesExchange |
P174867
|
FINISHED |
| Object | Chicago Mercantile Exchange |
—
|
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: Chicago Mercantile Exchange | Statement: [Chicago, hasFuturesExchange, Chicago Mercantile Exchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFuturesExchange Context triple: [Chicago, hasFuturesExchange, Chicago Mercantile Exchange]
-
A.
hasFuturesContracts
Indicates that one party holds or is engaged in futures contracts related to another entity, asset, or underlying reference.
-
B.
usesFuturesContractType
Indicates that one entity employs or is associated with a specific type of futures contract in its activities or relationships.
-
C.
isUsedInForexMarkets
Indicates that something is employed or traded as part of foreign exchange (forex) market activities.
-
D.
isExchangeTraded
Indicates that the entity is traded on a formal exchange or marketplace rather than over-the-counter or privately.
-
E.
hasSecondaryExchange
Indicates that an entity is additionally listed or traded on a secondary exchange beyond its primary market.
- F. None of above. chosen
Provenance (4 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c90790788190a1ed09adc86ed22d |
completed | May 3, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c814c26c81908f5c47285129ff2a |
completed | May 3, 2026, 3:59 a.m. |
Created at: May 1, 2026, 12:22 a.m.