Triple
T28147578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudy’s Rare Records |
E714524
|
entity |
| Predicate | stageAdaptationVenue |
P373
|
FINISHED |
| Object | Birmingham Repertory Theatre |
—
|
NE NERFINISHED |
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: Birmingham Repertory Theatre | Statement: [Rudy’s Rare Records, stageAdaptationVenue, Birmingham Repertory Theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageAdaptationVenue Context triple: [Rudy’s Rare Records, stageAdaptationVenue, Birmingham Repertory Theatre]
-
A.
stageAdaptation
Indicates that one work has been adapted into a performance intended for the stage, such as a play or musical.
-
B.
stageAdaptationForm
Indicates that one work is a stage adaptation (e.g., play, musical, performance script) derived from another work.
-
C.
startVenue
Indicates the venue or location where an event, journey, or activity begins.
-
D.
venue
chosen
Indicates the place or location where an event, activity, or interaction takes place.
-
E.
formerVenueComponentOf
Indicates that a venue previously functioned as a component or part of a larger venue or venue complex, but no longer holds that status.
- 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_69efd6b033208190bf74f80a147e2092 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 9:57 p.m.