Triple
T3397836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birmingham Repertory Theatre |
E71571
|
entity |
| Predicate | hasYouthTheatre |
P6626
|
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: [Birmingham Repertory Theatre, hasYouthTheatre, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYouthTheatre Context triple: [Birmingham Repertory Theatre, hasYouthTheatre, yes]
-
A.
hasYouthProgram
chosen
Indicates that an entity offers or is associated with an organized program or set of activities specifically designed for young people.
-
B.
hasYouthTeam
Indicates that an entity has an associated youth team that serves as its junior or developmental squad.
-
C.
performedPuppetryFor
Indicates that one entity carried out a puppetry performance for the benefit, entertainment, or purpose of another entity.
-
D.
theatreTraining
Indicates that one entity provides or engages in theatrical or drama-related training or education for another entity.
-
E.
hasMusicalTheatreOrigin
Indicates that something originates from, was first created for, or is primarily derived from musical theatre.
- 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb8c5816881909f91e6e9b81d29e3 |
completed | March 8, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:14 p.m.