Triple

T18861910
Position Surface form Disambiguated ID Type / Status
Subject NYSE: CBS.A E461330 entity
Predicate corporateActionExamples P87437 FINISHED
Object dividends LITERAL 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: dividends | Statement: [NYSE: CBS.A, corporateActionExamples, dividends]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: corporateActionExamples
Context triple: [NYSE: CBS.A, corporateActionExamples, dividends]
  • A. corporateActionType chosen
    Indicates the specific kind of corporate event or operation (such as mergers, dividends, or restructurings) that an entity undertakes or is involved in.
  • B. hasCorporateActionsOn
    Indicates that one entity performs, records, or is associated with corporate actions (such as dividends, splits, or mergers) that affect another entity.
  • C. corporateActionsProcessedThrough
    Indicates that corporate actions are executed, handled, or routed via a specified intermediary, system, or process.
  • D. hasCorporateActionHistory
    Indicates that an entity is associated with a record or sequence of past corporate actions or events that have affected it.
  • E. associatedCompanyAction
    Indicates that an action is performed by, on behalf of, or in direct connection with a particular company.
  • 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_69d8dcfb7b9c8190854e7b171b98ea2e completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c06184d88190bd05413a07a8c9ce completed April 20, 2026, 5:57 a.m.
PD Predicate disambiguation batch_69e48d2166b88190add38de96cedc65c completed April 19, 2026, 8:06 a.m.
Created at: April 10, 2026, 11:57 a.m.