Triple
T14675125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch Gothic |
E344615
|
entity |
| Predicate | styleTendency |
P19247
|
FINISHED |
| Object | functionalism over decoration |
—
|
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: functionalism over decoration | Statement: [Dutch Gothic, styleTendency, functionalism over decoration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleTendency Context triple: [Dutch Gothic, styleTendency, functionalism over decoration]
-
A.
styleTendsTo
chosen
Indicates that one style is generally inclined or likely to develop, appear, or be adopted in the direction of another style.
-
B.
fashionStyle
Indicates the characteristic way in which an entity dresses or presents themselves in terms of clothing and appearance.
-
C.
styleCategory
Indicates the stylistic classification or genre category that an item, work, or entity belongs to.
-
D.
styleDiversity
Indicates variation in the manner, form, or approach with which an entity presents, performs, or expresses something across different instances or contexts.
-
E.
trendy
Indicates that something is currently fashionable, popular, or in line with prevailing styles or tastes.
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb5666e648190b5faa07076f497b8 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.