Triple
T32016812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midnight (Sundance section) |
E817565
|
entity |
| Predicate | screeningSlot |
P178089
|
FINISHED |
| Object | midnight screenings |
—
|
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: midnight screenings | Statement: [Midnight (Sundance section), screeningSlot, midnight screenings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screeningSlot Context triple: [Midnight (Sundance section), screeningSlot, midnight screenings]
-
A.
screeningVenue
Indicates the place or location where a screening (such as a film or event showing) takes place.
-
B.
screeningsOccurDuring
Indicates that the time period of the screenings takes place within or overlaps with a specified time interval or event.
-
C.
screeningPattern
Indicates a recurring or structured way in which screenings (such as tests, evaluations, or showings) are scheduled, organized, or carried out between entities.
-
D.
screeningTime
Indicates the scheduled time at which a screening (such as a film, show, or test) is set to occur.
-
E.
screeningType
Indicates the specific method or category of screening applied in a screening process or evaluation.
- 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f707f380388190954b79d52a321921 |
completed | May 3, 2026, 8:31 a.m. |
Created at: May 1, 2026, 12:16 a.m.