Triple
T19093404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fabergé Limited |
E467344
|
entity |
| Predicate | creativeTheme |
P61406
|
FINISHED |
| Object | Imperial Russia-inspired motifs |
—
|
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: Imperial Russia-inspired motifs | Statement: [Fabergé Limited, creativeTheme, Imperial Russia-inspired motifs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creativeTheme Context triple: [Fabergé Limited, creativeTheme, Imperial Russia-inspired motifs]
-
A.
transformationTheme
Indicates a thematic relationship in which one entity centers on or explores the process, experience, or idea of transformation in another.
-
B.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
C.
themeInspiration
chosen
Indicates that one entity serves as the creative source or conceptual basis that inspires or shapes the theme expressed in another entity.
-
D.
PoseThemes
Indicates that a particular pose expresses, embodies, or is associated with certain thematic ideas or concepts.
-
E.
themeExamples
Indicates that the related entity serves as an example or illustration of the theme expressed by the subject.
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e34cf5e481908e1f180dacd5602f |
completed | April 20, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.