Triple
T16225021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hauptwache |
E393821
|
entity |
| Predicate | architecturalStyleOfGuardhouse |
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: [Hauptwache, architecturalStyleOfGuardhouse, Baroque]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architecturalStyleOfGuardhouse Context triple: [Hauptwache, architecturalStyleOfGuardhouse, Baroque]
-
A.
architecturalStyle
chosen
Indicates the architectural design tradition, movement, or style that characterizes the form and appearance of a structure or built work.
-
B.
architecturalStyleIncludes
Indicates that a structure, building, or design incorporates or exemplifies a particular architectural style as one of its defining characteristics.
-
C.
buildingStyleOfChamber
Indicates the architectural style or design type associated with a particular chamber.
-
D.
garrisonType
Indicates the specific kind or classification of military garrison associated with an entity.
-
E.
architecturalStyleCombines
Indicates that something incorporates elements or characteristics from multiple architectural styles into a single 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e23d24f9688190b670cfeb73332293 |
completed | April 17, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.