Triple
T1390111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Science Museum of Minnesota |
E29934
|
entity |
| Predicate | OmnitheaterType |
P16508
|
FINISHED |
| Object | IMAX-style large-format theater |
—
|
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: IMAX-style large-format theater | Statement: [Science Museum of Minnesota, OmnitheaterType, IMAX-style large-format theater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OmnitheaterType Context triple: [Science Museum of Minnesota, OmnitheaterType, IMAX-style large-format theater]
-
A.
theatreType
chosen
Indicates the specific category or kind of theatre associated with an entity, such as its format, style, or operational model.
-
B.
appliesToTheater
Indicates that something is relevant or applicable specifically to a theater or theatrical context.
-
C.
hasAuditorium
Indicates that one entity possesses or includes an auditorium as part of its facilities.
-
D.
theaterCommander
Indicates that an entity serves as the commanding authority over military operations within a specific theater or area of operations.
-
E.
theatricalSetting
Indicates the spatial or contextual environment in which a theatrical performance or dramatic action takes place.
- 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c35e023c8190b45688796d90534b |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4beffcf808190ab4cd0271257ce63 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.