Triple
T3485331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Brindley Theatre |
E73592
|
entity |
| Predicate | hasStudioSpace |
P4719
|
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: [The Brindley Theatre, hasStudioSpace, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStudioSpace Context triple: [The Brindley Theatre, hasStudioSpace, yes]
-
A.
hasStudio
Indicates that an entity (such as a film, game, or production) is associated with or produced by a particular studio.
-
B.
hasCentralSpace
Indicates that an entity includes or is characterized by a primary, central area or space within its overall structure.
-
C.
hasPublicSpaceAlong
Indicates that a public space (such as a park, plaza, or walkway) is located adjacent to or runs alongside the referenced feature or element.
-
D.
hasMainStudioShow
Indicates that an entity serves as the primary studio-based show associated with another entity (such as a network, channel, or program brand).
-
E.
hasCommunitySpace
chosen
Indicates that an entity provides or includes a shared physical or virtual area intended for communal use, activities, or gatherings.
- 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_69ad85cca8d4819088494e9f3340fab5 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbb8f205c8190aa6f7484ebad14bb |
completed | March 8, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69adae0935ac8190bfa8a8bd3dcd3301 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.