Triple
T2951836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BRK.A |
E79836
|
entity |
| Predicate | hasDividendPolicy |
P31242
|
FINISHED |
| Object | typically no cash dividend |
—
|
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: typically no cash dividend | Statement: [BRK.A, hasDividendPolicy, typically no cash dividend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDividendPolicy Context triple: [BRK.A, hasDividendPolicy, typically no cash dividend]
-
A.
paysDividends
Indicates that one entity distributes a portion of its earnings as dividends to another entity.
-
B.
dividendType
Indicates the classification of a dividend based on its nature or form (e.g., cash, stock, special), specifying what kind of dividend is being distributed.
-
C.
dividendFrequency
Indicates how often dividend payments are scheduled or distributed over a given period.
-
D.
hasCorporateActionsOn
Indicates that one entity performs, records, or is associated with corporate actions (such as dividends, splits, or mergers) that affect another entity.
-
E.
hasNotablePolicy
chosen
Indicates that an entity possesses a policy that is distinguished, significant, or otherwise noteworthy in its context.
- 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_69ad8b1276588190a374a0b12e0f7bdf |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98fcea5c8190b7d80de942bcb4f7 |
completed | March 8, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69ad960a70ac8190816b5ae3e8631031 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.