Triple
T38640647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adidas Finale Kyiv |
E938583
|
entity |
| Predicate | ballPanelDesign |
P145812
|
FINISHED |
| Object | star-shaped 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: star-shaped panels | Statement: [Adidas Finale Kyiv, ballPanelDesign, star-shaped panels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ballPanelDesign Context triple: [Adidas Finale Kyiv, ballPanelDesign, star-shaped panels]
-
A.
ballPanelTechnology
Indicates a technological relationship in which a ball interacts with, is controlled by, or is integrated into a panel-based system or interface.
-
B.
panels
chosen
Indicates that one entity is composed of, covered by, or divided into flat sections or segments formed by another entity.
-
C.
panel
Indicates that an entity serves as a panel, typically a group or board convened to discuss, judge, review, or make decisions about another entity or subject.
-
D.
boltDesign
Indicates a design relationship where one entity specifies or defines the bolt configuration, features, or parameters used in another entity.
-
E.
hasSculptedPanels
Indicates that an entity features or includes panels that have been sculpted as part of its design or structure.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.