Triple
T29654847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragoon |
E750236
|
entity |
| Predicate | visualColorScheme |
P29272
|
FINISHED |
| Object | blue and gold Protoss aesthetic |
—
|
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: blue and gold Protoss aesthetic | Statement: [Dragoon, visualColorScheme, blue and gold Protoss aesthetic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visualColorScheme Context triple: [Dragoon, visualColorScheme, blue and gold Protoss aesthetic]
-
A.
formerColorScheme
Indicates that an entity previously used a particular color scheme but no longer does so.
-
B.
hasColourScheme
chosen
Indicates that an entity is associated with a particular set or pattern of colors used in its design or appearance.
-
C.
graphicsTheme
Indicates the visual style or design motif that characterizes how something is graphically presented or themed.
-
D.
themeContrast
Indicates a relationship where two themes are compared or opposed to highlight their differences or tension.
-
E.
colorUse
Indicates that one entity uses, applies, or is associated with a particular color in its appearance, design, or representation.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 6:54 p.m.