Triple
T36162816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yerma (2016 Young Vic production) |
E1045921
|
entity |
| Predicate | usesSurtitleScreens |
P194964
|
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: [Yerma (2016 Young Vic production), usesSurtitleScreens, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSurtitleScreens Context triple: [Yerma (2016 Young Vic production), usesSurtitleScreens, yes]
-
A.
hasSubtitles
Indicates that one media item provides subtitle text or tracks that accompany another media item or its audio content.
-
B.
supportsSubtitleTrackSelection
Indicates that an entity provides functionality to choose or switch between available subtitle tracks.
-
C.
usesIntertitlesInSegment
Indicates that intertitles are employed within a specific segment of a work (such as a film or video) to convey information or dialogue.
-
D.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
-
E.
containsIntertitlesFrom
Indicates that one entity includes or incorporates intertitles that originate from another entity.
- F. None of above. chosen
Provenance (4 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_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
| PDg | Predicate description generation | batch_69fd91a44268819081b372296e3aa116 |
completed | May 8, 2026, 7:32 a.m. |
Created at: May 3, 2026, 4:08 p.m.