Triple
T2507603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adidas Telstar Durlast |
E52620
|
entity |
| Predicate | coating |
P37409
|
FINISHED |
| Object | Durlast polyurethane coating |
—
|
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: Durlast polyurethane coating | Statement: [Adidas Telstar Durlast, coating, Durlast polyurethane coating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coating Context triple: [Adidas Telstar Durlast, coating, Durlast polyurethane coating]
-
A.
typicalFinish
Indicates that an action, process, or event commonly or characteristically ends with a particular outcome or state.
-
B.
glazingType
Indicates the type or configuration of glazing (such as single, double, or special coatings) used in or applied to an element.
-
C.
cover
chosen
Indicates that one entity extends over, conceals, protects, or provides a surface or layer for another entity.
-
D.
packaging
Indicates that one entity serves as the container, wrapper, or enclosing material used to package another entity.
-
E.
materialDepicted
Indicates that a work or representation visually portrays or includes a particular material as part of its subject.
- 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_69ab4958e76481908a235377dd921c9e |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd65d6a988190aaaac8e98540a14f |
completed | March 7, 2026, 7:40 a.m. |
| PD | Predicate disambiguation | batch_69abd0bd996c8190ba8b9d6e4333b8d4 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.