Triple
T17393694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kunstmuseum Moritzburg Halle |
E422893
|
entity |
| Predicate | buildingUsedFor |
P1844
|
FINISHED |
| Object | museum purposes |
—
|
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: museum purposes | Statement: [Kunstmuseum Moritzburg Halle, buildingUsedFor, museum purposes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingUsedFor Context triple: [Kunstmuseum Moritzburg Halle, buildingUsedFor, museum purposes]
-
A.
buildingUsedBy
Indicates that a particular building is utilized or occupied by a specified entity for some purpose.
-
B.
locatedInBuildingUsedAs
Indicates that something is located inside a building that is being used for a specified purpose or function.
-
C.
buildingType
chosen
Indicates the specific category or function that characterizes what kind of building something is.
-
D.
publicBuilding
Indicates that a building is designated for public use or access, typically serving communal, governmental, or civic functions.
-
E.
buildingUsedSince
Indicates that a particular building has been in use starting from a specified point in time.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43abbd84881908af91bb7c9784026 |
completed | April 19, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.