Triple
T31427851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melk |
E801715
|
entity |
| Predicate | abbeyArchitecturalStyle |
P607
|
FINISHED |
| Object | Baroque |
—
|
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: Baroque | Statement: [Melk, abbeyArchitecturalStyle, Baroque]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abbeyArchitecturalStyle Context triple: [Melk, abbeyArchitecturalStyle, Baroque]
-
A.
parishChurchArchitectureStyle
Indicates the architectural style or design tradition in which a parish church is built or characterized.
-
B.
architecturalStyle
chosen
Indicates the architectural design tradition, movement, or style that characterizes the form and appearance of a structure or built work.
-
C.
hasCathedralStyle
Indicates that something possesses or is characterized by a particular architectural style associated with a cathedral.
-
D.
ecclesiasticalStyle
Indicates the formal religious or clerical style or title by which an ecclesiastical person is properly addressed.
-
E.
previousArchitecturalStyle
Indicates that one architectural style directly preceded another in the historical or developmental sequence of a building or design.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 8:54 p.m.