Triple
T24904421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hans Wilsdorf Foundation |
E623664
|
entity |
| Predicate | commercialActivityVia |
P158689
|
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, commercialActivityVia, Rolex SA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commercialActivityVia Context triple: [Hans Wilsdorf Foundation, commercialActivityVia, Rolex SA]
-
A.
commercialActivity
Indicates an action or relationship involving the buying, selling, or exchange of goods or services for profit or other economic gain.
-
B.
commercialActivityLevel
Indicates the intensity or extent of commercial or business-related activity occurring in a given context.
-
C.
commercialAccess
Indicates that an entity is permitted to use or access something for commercial or profit-generating purposes.
-
D.
commercialOperation
Indicates that an entity is engaged in or associated with a profit-oriented business activity or transaction.
-
E.
commercialSuccessIn
Indicates that something has achieved notable commercial success within a specified market, region, or domain.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f47b7f657c81908174590c811a3cbf |
completed | May 1, 2026, 10:07 a.m. |
Created at: April 18, 2026, 5:27 a.m.