Triple
T28900228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DIN 41612 |
E732931
|
entity |
| Predicate | hasTypicalPlating |
P7361
|
FINISHED |
| Object | tin or gold over nickel on contacts |
—
|
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: tin or gold over nickel on contacts | Statement: [DIN 41612, hasTypicalPlating, tin or gold over nickel on contacts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalPlating Context triple: [DIN 41612, hasTypicalPlating, tin or gold over nickel on contacts]
-
A.
hasPlate
Indicates that one entity possesses, is equipped with, or includes a plate as part of its attributes or components.
-
B.
plateType
chosen
Indicates the specific category or style of plate associated with an item or context.
-
C.
onPlate
Indicates that one entity is physically resting atop and supported by the surface of a plate.
-
D.
isTypicallyGarnishedWith
Indicates that one item is commonly used as a garnish or decorative finishing element for another.
-
E.
hasTypicalCut
Indicates that one entity is characterized by or associated with a standard or typical type of cut of 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: April 28, 2026, 8:02 a.m.