Triple
T21981868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lawler Exhibit Center |
E542859
|
entity |
| Predicate | hasExhibitionSchedule |
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: [Lawler Exhibit Center, hasExhibitionSchedule, rotating exhibitions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExhibitionSchedule Context triple: [Lawler Exhibit Center, hasExhibitionSchedule, rotating exhibitions]
-
A.
hasExhibition
Indicates that an entity organizes, hosts, or presents a particular exhibition.
-
B.
hasExhibitionProgram
Indicates that an entity (such as a venue or institution) organizes or offers a structured program of exhibitions.
-
C.
hasExhibitionScope
Indicates the thematic, geographic, temporal, or conceptual range and boundaries that define what an exhibition covers.
-
D.
hasExhibitionsAbout
Indicates that one entity organizes or presents exhibitions whose subject matter concerns another entity.
-
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. 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_69e0c48136b081908831fa907cc02e18 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1248de3688190a8d24cc8458851f2 |
completed | April 28, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:04 p.m.