Triple
T32177676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cummins Inc. |
E821897
|
entity |
| Predicate | primaryExchangeTicker |
P92459
|
FINISHED |
| Object | CMI |
E821897
|
NE 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: CMI | Statement: [Cummins Inc., primaryExchangeTicker, CMI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryExchangeTicker Context triple: [Cummins Inc., primaryExchangeTicker, CMI]
-
A.
primaryExchange
Indicates the main or most significant transfer or trade interaction occurring between two parties or systems.
-
B.
primaryExchangeFor
Indicates that one entity serves as the main or principal exchange platform or marketplace used for trading or transacting another entity.
-
C.
hasExchangeTicker
chosen
Indicates that an entity is identified or listed under a specific ticker symbol on a particular financial exchange.
-
D.
majorExchange
Indicates that an entity is a primary or significant trading venue where financial instruments are actively bought and sold.
-
E.
primaryExchangeForDerivatives
Indicates that one entity serves as the main trading venue or marketplace where derivative instruments related to another entity are listed or exchanged.
- F. None of above.
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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f46c2827c819094e0325854807753 |
completed | June 15, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:34 a.m.