Triple
T19604088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nibelungen Museum |
E470558
|
entity |
| Predicate | usesExhibitionForm |
P82275
|
FINISHED |
| Object | multimedia exhibition |
—
|
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: multimedia exhibition | Statement: [Nibelungen Museum, usesExhibitionForm, multimedia exhibition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesExhibitionForm Context triple: [Nibelungen Museum, usesExhibitionForm, multimedia exhibition]
-
A.
exhibitionUse
chosen
Indicates that something is used, intended, or designated for display in an exhibition or exhibit context.
-
B.
canExhibit
Indicates that one entity has the ability or potential to display, manifest, or show a particular property, behavior, or characteristic.
-
C.
exhibitFor
Indicates a relationship where something is displayed, presented, or shown for the benefit, use, or consideration of a particular audience, purpose, or entity.
-
D.
hasExhibition
Indicates that an entity organizes, hosts, or presents a particular exhibition.
-
E.
hasExhibitionFunction
Indicates that an entity serves the role or purpose of exhibiting, displaying, or presenting something (e.g., objects, works, or information).
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64081af6c8190868b73b07c874cd5 |
completed | April 20, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.