Triple
T12510824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Theatre |
E299070
|
entity |
| Predicate | isIndoorTheatre |
P105343
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Imperial Theatre, isIndoorTheatre, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIndoorTheatre Context triple: [Imperial Theatre, isIndoorTheatre, yes]
-
A.
isPartOfTheater
Indicates that one entity functions as a component, section, or subdivision within a larger theater (such as a theater building, complex, or organizational unit).
-
B.
theaterRequirement
Indicates that a certain condition, resource, or specification is required for a theater-related activity, production, or venue to be valid or properly supported.
-
C.
intendedTheatre
Indicates a relationship where an entity is planned, designed, or meant to be performed, shown, or take place in a particular theatre.
-
D.
theaterType
Indicates the specific kind or category of theater associated with an entity (e.g., cinema, opera house, drama theater).
-
E.
theaterSupport
Indicates that one entity provides assistance, resources, or services to support another entity in the context of theater or theatrical activities.
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954b867dc8190af8a70f797e4d133 |
completed | April 10, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69d954096af88190b6be81b008c82139 |
completed | April 10, 2026, 7:48 p.m. |
| PDg | Predicate description generation | batch_69d954b715fc819091fa84430be46273 |
completed | April 10, 2026, 7:51 p.m. |
Created at: April 8, 2026, 9:57 p.m.