Triple
T7821404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hall for Cornwall |
E181136
|
entity |
| Predicate | openedAsTheatre |
P72431
|
FINISHED |
| Object | 1997 |
—
|
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: 1997 | Statement: [Hall for Cornwall, openedAsTheatre, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsTheatre Context triple: [Hall for Cornwall, openedAsTheatre, 1997]
-
A.
introducedInTheater
Indicates that something (such as a film, play, or performance) was first presented or made available to the public in a theater setting.
-
B.
theatreOpened
chosen
Indicates that a theatre began operating or was officially opened at a particular time or event.
-
C.
reopenedAsTheater
Indicates that a venue or building, previously closed or used differently, has been opened again specifically to function as a theater.
-
D.
servedInTheatres
Indicates that a film or performance was publicly exhibited in movie theaters or similar cinema venues.
-
E.
servedInTheatre
Indicates that an individual performed military or service duties within a specific theater of operations or geographic area during a conflict or campaign.
- 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_69ca828153f48190bdb27ac46f8e0745 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cafa083fe88190a77efb7cfee4bd6f |
completed | March 30, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69cae91ae008819098e56bbe51143b31 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:41 p.m.