Triple
T24228132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ležáky |
E601650
|
entity |
| Predicate | hasMuseumExhibition |
P1513
|
FINISHED |
| Object | exposition on Nazi reprisals |
—
|
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: exposition on Nazi reprisals | Statement: [Ležáky, hasMuseumExhibition, exposition on Nazi reprisals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMuseumExhibition Context triple: [Ležáky, hasMuseumExhibition, exposition on Nazi reprisals]
-
A.
hasExhibition
chosen
Indicates that an entity organizes, hosts, or presents a particular exhibition.
-
B.
hasExhibitionsAbout
Indicates that one entity organizes or presents exhibitions whose subject matter concerns another entity.
-
C.
hasExhibits
Indicates that an entity (such as a museum, gallery, or event) displays or presents certain items, artworks, or objects as part of its collection or show.
-
D.
hasExhibitedAt
Indicates that an entity has displayed or presented its work at a particular event, venue, or 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_69e29538aafc8190a2386fdebbd1393b |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f287e11e188190bd257f24cb593039 |
completed | April 29, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:01 a.m.