Triple
T28569850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Museum of Literature of Ukraine |
E722782
|
entity |
| Predicate | hasExhibitionRole |
P174698
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [National Museum of Literature of Ukraine, hasExhibitionRole, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExhibitionRole Context triple: [National Museum of Literature of Ukraine, hasExhibitionRole, yes]
-
A.
hasExhibition
Indicates that an entity organizes, hosts, or presents a particular exhibition.
-
B.
hasExhibitionScope
Indicates the thematic, geographic, temporal, or conceptual range and boundaries that define what an exhibition covers.
-
C.
hasExhibitionFunction
Indicates that an entity serves the role or purpose of exhibiting, displaying, or presenting something (e.g., objects, works, or information).
-
D.
hasExhibitionsAbout
Indicates that one entity organizes or presents exhibitions whose subject matter concerns another entity.
-
E.
hasExhibitionLabel
Indicates that an entity is associated with a specific exhibition label used for display or interpretive purposes in an exhibition context.
- 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6c5b7e46081909975b05f7298cc0e |
completed | May 3, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c49069e48190a3486b6254a6645b |
completed | May 3, 2026, 3:44 a.m. |
Created at: April 28, 2026, 4:09 a.m.