Triple
T27065568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philosophy di Alberta Ferretti |
E685163
|
entity |
| Predicate | designAesthetic |
P102534
|
FINISHED |
| Object | contemporary |
—
|
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: contemporary | Statement: [Philosophy di Alberta Ferretti, designAesthetic, contemporary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designAesthetic Context triple: [Philosophy di Alberta Ferretti, designAesthetic, contemporary]
-
A.
designAspect
Indicates that one entity represents a particular design-related feature, characteristic, or consideration of another entity.
-
B.
visualDesignInspiredBy
Indicates that the visual design of one entity is influenced, modeled, or derived from the visual style or appearance of another entity.
-
C.
associatedAesthetic
chosen
Indicates a relationship where one entity is linked to or characterized by a particular aesthetic style, quality, or visual/theme-based sensibility.
-
D.
productionDesignStyle
Indicates the visual and aesthetic approach used in designing the overall look and environment of a production.
-
E.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
- 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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 27, 2026, 8:24 a.m.