Triple
T28390760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Classic theme |
E719149
|
entity |
| Predicate | UIElementStyle |
P124216
|
FINISHED |
| Object | 3D beveled controls |
—
|
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: 3D beveled controls | Statement: [Classic theme, UIElementStyle, 3D beveled controls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UIElementStyle Context triple: [Classic theme, UIElementStyle, 3D beveled controls]
-
A.
featuresStyleElement
chosen
Indicates that one entity includes or incorporates a particular style-related element as part of its composition or design.
-
B.
styleContext
Indicates that one entity provides the stylistic or formatting context within which another entity is interpreted or rendered.
-
C.
styleContribution
Indicates a relationship where one entity contributes to or influences the stylistic characteristics or aesthetic qualities of another.
-
D.
coreDesignStyle
Indicates the primary or defining design style that characterizes an entity’s overall aesthetic or structural approach.
-
E.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64cec950881909d89fd56511514a2 |
completed | May 2, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 1:13 a.m.