Triple
T28147736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Black and White Minstrel Show |
E714528
|
entity |
| Predicate | stageShowVenue |
P112843
|
FINISHED |
| Object | Victoria Palace 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: Victoria Palace Theatre | Statement: [The Black and White Minstrel Show, stageShowVenue, Victoria Palace Theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageShowVenue Context triple: [The Black and White Minstrel Show, stageShowVenue, Victoria Palace Theatre]
-
A.
hasVenueFor
chosen
Indicates that one entity provides or serves as the location or setting where an event, activity, or function takes place for another entity.
-
B.
hasVenueName
Indicates that an entity has a specific name used to identify the venue where an event or activity takes place.
-
C.
startVenue
Indicates the venue or location where an event, journey, or activity begins.
-
D.
hostsVenue
Indicates that an entity provides or manages a location where an event or activity takes place.
-
E.
hasVenueIn
Indicates that an event, activity, or occurrence takes place at a specific venue located within a particular geographic area or location.
- 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_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 9:57 p.m.