Triple
T18861208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | i-Cockpit interior design |
E461313
|
entity |
| Predicate | dashboardStyle |
P25796
|
FINISHED |
| Object | clean horizontal lines |
—
|
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: clean horizontal lines | Statement: [i-Cockpit interior design, dashboardStyle, clean horizontal lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dashboardStyle Context triple: [i-Cockpit interior design, dashboardStyle, clean horizontal lines]
-
A.
platformAppearance
Indicates how an entity is visually presented or styled on a particular platform or interface.
-
B.
styleFor
Indicates a relationship where one entity defines, specifies, or is used as the style or styling configuration applied to another entity.
-
C.
featuresStyle
chosen
Indicates that one entity exhibits, incorporates, or is characterized by a particular style associated with another entity.
-
D.
styleWhite
Indicates that one entity has a white style, appearance, or coloration in relation to another or within a given context.
-
E.
graphicsTheme
Indicates the visual style or design motif that characterizes how something is graphically presented or themed.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c060bfc4819092ac591692a6ccd5 |
completed | April 20, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.