Triple
T3428659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TAG Heuer Link |
E72284
|
entity |
| Predicate | braceletMaterial |
P1272
|
FINISHED |
| Object | stainless steel |
—
|
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: stainless steel | Statement: [TAG Heuer Link, braceletMaterial, stainless steel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: braceletMaterial Context triple: [TAG Heuer Link, braceletMaterial, stainless steel]
-
A.
associatedMetal
Indicates a relationship where one entity is linked or connected to a particular metal, such as by composition, usage, origin, or symbolic association.
-
B.
materialUsed
chosen
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
C.
hasRingComposition
Indicates that one entity is composed of, or structurally organized around, a ring-like arrangement or circular structure.
-
D.
caratWeight
Indicates the weight of a gemstone or diamond, measured in carats, associated with an item or entity.
-
E.
hasClasps
Indicates that one entity is equipped with or features clasps that fasten, secure, or attach it to another entity or its parts.
- 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.