Triple
T24904428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hans Wilsdorf Foundation |
E623664
|
entity |
| Predicate | beneficiaryOfDividendsFrom |
P80828
|
FINISHED |
| Object | Rolex SA |
—
|
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: Rolex SA | Statement: [Hans Wilsdorf Foundation, beneficiaryOfDividendsFrom, Rolex SA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beneficiaryOfDividendsFrom Context triple: [Hans Wilsdorf Foundation, beneficiaryOfDividendsFrom, Rolex SA]
-
A.
paysDividendsThrough
Indicates that one entity distributes dividend payments to another entity by means of a specified intermediary or mechanism.
-
B.
dividendEntitlement
chosen
Indicates that one entity has the right to receive dividend payments associated with another entity.
-
C.
paysDividends
Indicates that one entity distributes a portion of its earnings as dividends to another entity.
-
D.
dividendsBasedOn
Indicates that the amount or occurrence of dividends is determined or calculated based on a specified factor or reference.
-
E.
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.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:27 a.m.