Triple
T263186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Historical Village Museum |
E5796
|
entity |
| Predicate | hasExhibitTheme |
P5290
|
FINISHED |
| Object | Dutch immigration to Iowa |
—
|
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: Dutch immigration to Iowa | Statement: [Historical Village Museum, hasExhibitTheme, Dutch immigration to Iowa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExhibitTheme Context triple: [Historical Village Museum, hasExhibitTheme, Dutch immigration to Iowa]
-
A.
exhibitTheme
chosen
Indicates that something (such as a work, event, or presentation) presents, embodies, or is organized around a particular theme.
-
B.
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.
-
C.
hasExhibition
Indicates that an entity organizes, hosts, or presents a particular exhibition.
-
D.
hasInteractiveExhibits
Indicates that something contains exhibits designed for active participation or engagement by the audience.
-
E.
hasMuseumType
Indicates that an entity is classified as a museum of a specific type or category.
- 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_69a258dd8ea08190ac554a1cc8dfd8c3 |
completed | Feb. 28, 2026, 2:54 a.m. |
| NER | Named-entity recognition | batch_69a25d8c7f448190af9145256f994177 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b6e07748190834022a65ba6d803 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.