Triple
T21752416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSRGY |
E536946
|
entity |
| Predicate | dividendsBasedOn |
P145236
|
FINISHED |
| Object | Nestlé S.A. 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: Nestlé S.A. dividends | Statement: [NSRGY, dividendsBasedOn, Nestlé S.A. dividends]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dividendsBasedOn Context triple: [NSRGY, dividendsBasedOn, Nestlé S.A. dividends]
-
A.
dividendEntitlement
Indicates that one entity has the right to receive dividend payments associated with 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.
dividendPolicy
Indicates the strategy or rules a company follows in deciding whether, when, and how much profit to distribute to shareholders as dividends.
-
D.
isDividendPaying
Indicates that an entity (typically a financial instrument or company) pays dividends to its shareholders.
-
E.
paysDividendsThrough
Indicates that one entity distributes dividend payments to another entity by means of a specified intermediary or mechanism.
- F. None of above. chosen
Provenance (4 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01d8b8b9c8190b1f6a8bc25d69dbb |
completed | April 28, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69f3ed4408190a4a78410bf660c44 |
completed | April 20, 2026, 9:48 p.m. |
Created at: April 16, 2026, 6:50 p.m.