Triple
T1623358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aestheticism |
E35081
|
entity |
| Predicate | aestheticPreference |
P16367
|
FINISHED |
| Object | formal beauty and harmony |
—
|
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: formal beauty and harmony | Statement: [Aestheticism, aestheticPreference, formal beauty and harmony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aestheticPreference Context triple: [Aestheticism, aestheticPreference, formal beauty and harmony]
-
A.
styleTendsTo
Indicates that one style is generally inclined or likely to develop, appear, or be adopted in the direction of another style.
-
B.
marketPreference
Indicates a relationship where one entity favors, targets, or prioritizes a particular market or market segment over others.
-
C.
appearance
Indicates how something looks or seems to an observer, including its visible form, condition, or outward impression.
-
D.
artisticCharacteristic
chosen
Indicates that one entity possesses or exhibits a particular artistic quality, style, or trait in relation to another.
-
E.
artisticStyle
Indicates the artistic movement, style, or aesthetic approach that characterizes how something is created or visually expressed.
- 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_69a886023194819080a3fccd6e325d0e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf4a0ef748190ae52b9656474c0ef |
completed | March 6, 2026, 3:37 p.m. |
| PD | Predicate disambiguation | batch_69a907c731808190a1d998155041b3c1 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.