Triple
T34098885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viacom Inc. |
E874509
|
entity |
| Predicate | hasFormerTickerSymbol |
P23749
|
FINISHED |
| Object | VIAB |
—
|
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: VIAB | Statement: [Viacom Inc., hasFormerTickerSymbol, VIAB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerTickerSymbol Context triple: [Viacom Inc., hasFormerTickerSymbol, VIAB]
-
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.
associatedCompanyTickerSuccessor
Indicates that one company ticker symbol is the successor or replacement for another company ticker symbol in an association or mapping.
-
C.
underlyingCompanyFormerName
Indicates that the object is a former or previous legal name by which the underlying company (the subject) was known.
-
D.
associatedCompanyTradedAs
Indicates that a company is linked to the stock ticker, trading name, or market symbol under which it is publicly traded.
-
E.
hasCorporateTickerRoot
Indicates that a company’s stock ticker symbol is derived from or based on the specified root string.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
Created at: May 1, 2026, 1:53 a.m.