Triple
T23010587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RY |
E572893
|
entity |
| Predicate | isDividendAristocratInCanada |
P54061
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [RY, isDividendAristocratInCanada, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDividendAristocratInCanada Context triple: [RY, isDividendAristocratInCanada, true]
-
A.
isDividendAristocrat
chosen
Indicates that an entity has consistently increased its dividend payouts for a long, defined period, qualifying it as a “dividend aristocrat.”
-
B.
isDividendPaying
Indicates that an entity (typically a financial instrument or company) pays dividends to its shareholders.
-
C.
paysDividends
Indicates that one entity distributes a portion of its earnings as dividends to another entity.
-
D.
paysDividendsThrough
Indicates that one entity distributes dividend payments to another entity by means of a specified intermediary or mechanism.
-
E.
dividendEligibility
Indicates that an entity (such as a shareholder or security) qualifies to receive a declared dividend for a given distribution event.
- 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18359f5548190b15a139eb09e30a0 |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:51 p.m.