Triple
T35445303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salon of 1717 |
E1024465
|
entity |
| Predicate | artStylePresented |
P27951
|
FINISHED |
| Object | Rococo |
—
|
NE NERFINISHED |
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: Rococo | Statement: [Salon of 1717, artStylePresented, Rococo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artStylePresented Context triple: [Salon of 1717, artStylePresented, Rococo]
-
A.
artisticStyle
Indicates the artistic movement, style, or aesthetic approach that characterizes how something is created or visually expressed.
-
B.
exhibitStyle
chosen
Indicates that an entity displays, demonstrates, or embodies a particular style or manner of expression.
-
C.
artForm
Indicates the type or category of artistic expression that characterizes or defines something (e.g., painting, music, dance).
-
D.
inTheStyleOf
Indicates that one entity is created, performed, or presented in a manner that imitates or closely resembles the characteristic style of another entity.
-
E.
styleFor
Indicates a relationship where one entity defines, specifies, or is used as the style or styling configuration applied to 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_69f76df8089481909f0018266ee881b7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7962095a481909719282611283f4d |
completed | May 3, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:04 p.m.