Triple
T19737438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Revival |
E474022
|
entity |
| Predicate | stylisticElement |
P137145
|
FINISHED |
| Object | Corinthian columns |
—
|
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: Corinthian columns | Statement: [Roman Revival, stylisticElement, Corinthian columns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stylisticElement Context triple: [Roman Revival, stylisticElement, Corinthian columns]
-
A.
stylisticEffect
Indicates the relationship where one element produces, contributes to, or embodies a particular stylistic impact or impression on another.
-
B.
stylisticFocus
Indicates a relationship where something is primarily concerned with, emphasizes, or is characterized by a particular style or set of stylistic features.
-
C.
stylisticSignificance
Indicates that one entity holds importance or meaning specifically because of its style or manner of expression in relation to another entity or context.
-
D.
stylisticRange
Indicates the range or spectrum of styles that characterize or can be applied to something.
-
E.
stylingFeature
Indicates a visual or design-related characteristic applied to an entity, such as formatting, layout, or aesthetic treatment.
- F. None of above. chosen
Provenance (4 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6515ea688819097b6838e6a3b3d4a |
completed | April 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:47 p.m.