Triple
T35672827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porcelain Room |
E1030771
|
entity |
| Predicate | decorativeArtStyle |
P86416
|
FINISHED |
| Object | Rococo porcelain |
—
|
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: Rococo porcelain | Statement: [Porcelain Room, decorativeArtStyle, Rococo porcelain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decorativeArtStyle Context triple: [Porcelain Room, decorativeArtStyle, Rococo porcelain]
-
A.
decorativeCategory
Indicates that one entity is classified as belonging to a particular decorative style, theme, or ornamentation category of another entity.
-
B.
ornamentationStyle
chosen
Indicates the decorative design or stylistic approach applied as ornamentation to an entity.
-
C.
artSpecialty
Indicates that an entity’s primary focus, expertise, or specialization is in a particular art form or artistic domain.
-
D.
rockArtStyle
Indicates that one entity is characterized by, or associated with, a particular style or tradition of rock art.
-
E.
hasPotteryDecoration
Indicates that an object or artifact bears a specific type or style of decorative treatment applied to its pottery surface.
- 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.