Triple
T32672511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tonino Lamborghini |
E835334
|
entity |
| Predicate | productCategoryDesigned |
P143050
|
FINISHED |
| Object | wristwatches |
—
|
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: wristwatches | Statement: [Tonino Lamborghini, productCategoryDesigned, wristwatches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productCategoryDesigned Context triple: [Tonino Lamborghini, productCategoryDesigned, wristwatches]
-
A.
productTypeDesigned
chosen
Indicates that one entity is the type or category of product for which another entity has been specifically designed.
-
B.
designCategory
Indicates that one entity is classified under a particular design-related category or type.
-
C.
designedIn
Indicates that something was created, planned, or conceived during a particular time period or at a specific location.
-
D.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
-
E.
designsFor
Indicates that one entity creates or plans something specifically intended to serve, suit, or be used by another entity.
- 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_69f3493134b48190aa3c8cb523bd3800 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: May 1, 2026, 1:09 a.m.