Triple
T26288313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Königswart Castle |
E661198
|
entity |
| Predicate | laterStyleElements |
P124216
|
FINISHED |
| Object | Classicism |
—
|
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: Classicism | Statement: [Königswart Castle, laterStyleElements, Classicism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterStyleElements Context triple: [Königswart Castle, laterStyleElements, Classicism]
-
A.
featuresStyleElement
chosen
Indicates that one entity includes or incorporates a particular style-related element as part of its composition or design.
-
B.
styledAs
Indicates that one entity is presented, formatted, or designed in the manner, appearance, or aesthetic of another entity.
-
C.
stylingFeature
Indicates a visual or design-related characteristic applied to an entity, such as formatting, layout, or aesthetic treatment.
-
D.
semanticsStyle
Indicates the manner or stylistic approach in which meaning is expressed or interpreted in a communicative act or representation.
-
E.
refinedStyle
Indicates that an entity exhibits a polished, elegant, and carefully developed manner or aesthetic in its presentation or behavior.
- 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_69ee812bbd448190be4d7478b057990a |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 26, 2026, 10:06 p.m.