Triple
T29515717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panorama Museum Bad Frankenhausen |
E748789
|
entity |
| Predicate | hasDomeBuilding |
P173262
|
FINISHED |
| Object | cylindrical panorama hall |
—
|
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: cylindrical panorama hall | Statement: [Panorama Museum Bad Frankenhausen, hasDomeBuilding, cylindrical panorama hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDomeBuilding Context triple: [Panorama Museum Bad Frankenhausen, hasDomeBuilding, cylindrical panorama hall]
-
A.
hasDomeOrTower
Indicates that one entity possesses or features a dome or a tower as part of its structure.
-
B.
hasDomeDesign
Indicates that one entity features or incorporates the dome design of another entity.
-
C.
hasDomeDecoration
Indicates that an entity’s dome is adorned with specific decorative elements or ornamentation.
-
D.
hasDomeOrSpire
Indicates that one entity possesses or features a dome or spire as part of its structure.
-
E.
hasDomeStyle
Indicates that one entity (typically a building or structure) possesses a dome characterized by a particular architectural style or form.
- 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_69f0bd461c208190bec20bbf24e02cc5 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 28, 2026, 4:37 p.m.