Triple
T36162798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yerma (2016 Young Vic production) |
E1045921
|
entity |
| Predicate | producerTheatre |
P33162
|
FINISHED |
| Object | Young Vic |
—
|
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: Young Vic | Statement: [Yerma (2016 Young Vic production), producerTheatre, Young Vic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producerTheatre Context triple: [Yerma (2016 Young Vic production), producerTheatre, Young Vic]
-
A.
theatricalProducer
chosen
Indicates that one entity serves as the theatrical producer of a performance, production, or show involving the other entity.
-
B.
theaterProduction
Indicates a relationship where a theatrical work is produced or staged, typically linking the production event to the play, venue, or organizing entity.
-
C.
operatorOfTheatre
Indicates a relationship where an entity operates, manages, or runs a theatre.
-
D.
theatreOf
Indicates that an event, action, or operation takes place within or is primarily associated with a particular theatre or venue.
-
E.
theatre
Indicates that an entity is a theater or is associated with theatrical performances or activities.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff0214d7348190904688376df99bce |
completed | May 9, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69feffd62fec8190a855922c8b3c57cf |
completed | May 9, 2026, 9:35 a.m. |
Created at: May 3, 2026, 4:08 p.m.