Triple
T15540321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adidas Roteiro |
E370457
|
entity |
| Predicate | ballPanelTechnology |
P119103
|
FINISHED |
| Object | thermal bonding |
—
|
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: thermal bonding | Statement: [Adidas Roteiro, ballPanelTechnology, thermal bonding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ballPanelTechnology Context triple: [Adidas Roteiro, ballPanelTechnology, thermal bonding]
-
A.
hasPanel
Indicates that one entity includes, is equipped with, or is associated with a panel as a component or feature.
-
B.
platformShowcased
Indicates that a platform is prominently presented or highlighted, typically to draw attention to its features, capabilities, or offerings.
-
C.
panelFound
Indicates that a specific panel has been located, identified, or successfully detected in a given context or environment.
-
D.
viewOnTechnology
Indicates how an entity perceives, evaluates, or holds opinions about technology and its role or impact.
-
E.
panelControl
Indicates a relationship where one entity controls, manages, or operates a panel associated with another entity.
- F. None of above. chosen
Provenance (4 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04430b5188190a555a3cd4fb0c61c |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:07 a.m.