Triple
T3428623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TAG Heuer Link |
E72284
|
entity |
| Predicate | braceletDesign |
P1529
|
FINISHED |
| Object | S-shaped links |
—
|
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: S-shaped links | Statement: [TAG Heuer Link, braceletDesign, S-shaped links]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: braceletDesign Context triple: [TAG Heuer Link, braceletDesign, S-shaped links]
-
A.
designsFor
Indicates that one entity creates or plans something specifically intended to serve, suit, or be used by another entity.
-
B.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
-
C.
hasDesign
chosen
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
D.
collarFeature
Indicates that one entity has a specific characteristic, detail, or attribute related to a collar.
-
E.
ribbonDesignFeature
Indicates a design-related characteristic or attribute that is specifically associated with a ribbon.
- 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_69ad85ae14308190bcbc25cfa0246c0b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb983f4608190abcc27aa7b926deb |
completed | March 8, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69adadfea024819094b41a13bc004bda |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.