Triple
T15493277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spider-Man Noir |
E378749
|
entity |
| Predicate | settingAesthetic |
P102534
|
FINISHED |
| Object | black-and-white |
—
|
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: black-and-white | Statement: [Spider-Man Noir, settingAesthetic, black-and-white]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingAesthetic Context triple: [Spider-Man Noir, settingAesthetic, black-and-white]
-
A.
associatedAesthetic
chosen
Indicates a relationship where one entity is linked to or characterized by a particular aesthetic style, quality, or visual/theme-based sensibility.
-
B.
aestheticRole
Indicates the role or function something has within an aesthetic or artistic context (e.g., as artwork, decoration, or design element).
-
C.
stylingTool
Indicates a tool or instrument used to style, shape, or arrange something (typically hair, clothing, or design elements).
-
D.
styleFor
Indicates a relationship where one entity defines, specifies, or is used as the style or styling configuration applied to another entity.
-
E.
styleTendsTo
Indicates that one style is generally inclined or likely to develop, appear, or be adopted in the direction of another style.
- 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03fad723481908d2aa33e8f065f2f |
completed | April 16, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:49 a.m.