Triple
T34936149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The McClatchy Company |
E1007574
|
entity |
| Predicate | hasFormerStockTicker |
P23749
|
FINISHED |
| Object | NYSE:MNI |
—
|
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:MNI | Statement: [The McClatchy Company, hasFormerStockTicker, NYSE:MNI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerStockTicker Context triple: [The McClatchy Company, hasFormerStockTicker, NYSE:MNI]
-
A.
formerTickerSymbol
chosen
Indicates that one entity was previously used as the stock ticker symbol for another entity, but is no longer its current ticker symbol.
-
B.
hasCorporateTickerRoot
Indicates that a company’s stock ticker symbol is derived from or based on the specified root string.
-
C.
associatedCompanyTickerSuccessor
Indicates that one company ticker symbol is the successor or replacement for another company ticker symbol in an association or mapping.
-
D.
hasStockExchange
Indicates that an entity is associated with or listed on a particular stock exchange.
-
E.
underlyingCompanyTicker
Indicates that one entity is the stock ticker symbol corresponding to the underlying company of another financial instrument or entity.
- 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_69f76dc513fc819084a1ff52abbfa5bc |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: May 3, 2026, 4 p.m.