Triple
T24451499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coos Art Museum |
E616550
|
entity |
| Predicate | exhibitionSchedule |
P146151
|
FINISHED |
| Object | rotating exhibitions |
—
|
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: rotating exhibitions | Statement: [Coos Art Museum, exhibitionSchedule, rotating exhibitions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exhibitionSchedule Context triple: [Coos Art Museum, exhibitionSchedule, rotating exhibitions]
-
A.
hasExhibitionSchedule
chosen
Indicates that an entity has an associated timetable or plan specifying when its exhibitions or displays will take place.
-
B.
exhibitedDuring
Indicates that something was presented, displayed, or shown over the course of a specified time period or event.
-
C.
exhibitionSeries
Indicates that multiple exhibitions are related and organized as parts of the same overarching series or program.
-
D.
organizedExhibitionsIn
Indicates that an entity arranged, coordinated, or managed exhibitions that took place in a specified location or venue.
-
E.
hasExhibitionsAbout
Indicates that one entity organizes or presents exhibitions whose subject matter concerns another entity.
- 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_69e2d7edca608190aafefc8877a1b4da |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2985848748190ae0e436b2e83f249 |
completed | April 29, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:18 a.m.