Triple
T34871703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adidas Europass Gloria |
E1005768
|
entity |
| Predicate | hasPanelDesign |
P141367
|
FINISHED |
| Object | thermally bonded panels |
—
|
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: thermally bonded panels | Statement: [Adidas Europass Gloria, hasPanelDesign, thermally bonded panels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPanelDesign Context triple: [Adidas Europass Gloria, hasPanelDesign, thermally bonded panels]
-
A.
hasPanel
Indicates that one entity includes, is equipped with, or is associated with a panel as a component or feature.
-
B.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
C.
hasSculptedPanels
Indicates that an entity features or includes panels that have been sculpted as part of its design or structure.
-
D.
hasDesignSide
Indicates that one entity is located on, associated with, or corresponds to a particular side or face of another entity’s design.
-
E.
hasPanelAppearance
chosen
Indicates that an entity features or exhibits a particular panel-based visual or structural appearance.
- 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_69f76dbde1c08190a24e7f9beb564c8d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffac35ac5481908b6bdfd5bbe8c76e |
completed | May 9, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69ffabbfd2548190964c851496bbbaee |
completed | May 9, 2026, 9:48 p.m. |
Created at: May 3, 2026, 4 p.m.