Triple
T33898190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuschinski Theater |
E868971
|
entity |
| Predicate | hasSubtitledScreenings |
P53376
|
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: [Tuschinski Theater, hasSubtitledScreenings, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubtitledScreenings Context triple: [Tuschinski Theater, hasSubtitledScreenings, yes]
-
A.
hasSubtitles
chosen
Indicates that one media item provides subtitle text or tracks that accompany another media item or its audio content.
-
B.
hasFilmScreenings
Indicates that a film is scheduled to be shown at one or more specific screenings or venues.
-
C.
languageOfScreenings
Indicates the language in which screenings (such as film or event showings) are presented.
-
D.
screenedIn
Indicates that one entity has been evaluated or assessed to determine whether it meets certain criteria for inclusion, participation, or further consideration in relation to another entity.
-
E.
screeningsOccurDuring
Indicates that the time period of the screenings takes place within or overlaps with a specified time interval or event.
- 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_69f34997703c8190866b1d404bce531f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff779e3f0c8190a861f1e4000fd9d9 |
completed | May 9, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69ff77202638819086e4b9f9c0bc7b31 |
completed | May 9, 2026, 6:04 p.m. |
Created at: May 1, 2026, 1:48 a.m.