Triple
T36162722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yerma (Young Vic production) |
E1045919
|
entity |
| Predicate | transferLocation |
P57570
|
FINISHED |
| Object | West End |
—
|
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: West End | Statement: [Yerma (Young Vic production), transferLocation, West End]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferLocation Context triple: [Yerma (Young Vic production), transferLocation, West End]
-
A.
transferDestination
chosen
Indicates the entity that serves as the receiving end or target location of a transfer from another entity.
-
B.
transferBetween
Indicates a movement or handover of something from one entity to another, typically changing its location, ownership, or control between them.
-
C.
transportFrom
Indicates that something or someone is moved or carried away starting from a specified origin location.
-
D.
transferWithinSystem
Indicates the movement or reassignment of something from one part or component of a system to another part or component within the same overall system.
-
E.
transferFeature
Indicates a relationship where a feature, attribute, or capability is moved or reassigned from one entity to another.
- 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_69ff76ac40988190a34d858b5472ee2b |
completed | May 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69ff760a90948190a12fcb80e6e3e14b |
completed | May 9, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:08 p.m.