Triple
T28903254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OMC |
E733006
|
entity |
| Predicate | hasExchangeTickerFormat |
P63922
|
FINISHED |
| Object | NYSE:OMC |
—
|
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: NYSE:OMC | Statement: [OMC, hasExchangeTickerFormat, NYSE:OMC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExchangeTickerFormat Context triple: [OMC, hasExchangeTickerFormat, NYSE:OMC]
-
A.
hasExchangeTicker
Indicates that an entity is identified or listed under a specific ticker symbol on a particular financial exchange.
-
B.
exchangeTickerFormat
chosen
Indicates the specific formatting convention used to represent a security’s ticker symbol on a particular exchange.
-
C.
hasTickerFormat
Indicates that an entity’s ticker symbol follows a specified structural or syntactic format.
-
D.
hasTradingFormat
Indicates that one entity is associated with, or conducted according to, a particular trading format or mode of trade.
-
E.
hasUnderlyingExchangeTicker
Indicates that one financial instrument is based on, or derives its value from, another instrument identified by a specific exchange ticker.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 28, 2026, 8:04 a.m.