Triple
T2924310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MONA (Museum of Old and New Art) |
E78805
|
entity |
| Predicate | exhibitionApproach |
P43958
|
FINISHED |
| Object | thematic curation |
—
|
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: thematic curation | Statement: [MONA (Museum of Old and New Art), exhibitionApproach, thematic curation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exhibitionApproach Context triple: [MONA (Museum of Old and New Art), exhibitionApproach, thematic curation]
-
A.
exhibition
Indicates that an entity is organizing, hosting, or serving as a public display or presentation of another entity (such as artworks, objects, or information).
-
B.
exhibitionType
Indicates the specific category or kind of exhibition associated with an entity (e.g., art show, trade fair, scientific exhibit).
-
C.
exhibitionSource
Indicates the origin or provider from which an exhibition or displayed work is sourced or obtained.
-
D.
exhibitStyle
Indicates that an entity displays, demonstrates, or embodies a particular style or manner of expression.
-
E.
exhibitionPolicy
Indicates the rules or guidelines governing how an item may be displayed, presented, or exhibited.
- 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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97fd89d88190bc7db4b39058ae3a |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9603ddd88190b8bf91bc7517cc21 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f520208190a4dc43372004555f |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:55 p.m.