Triple
T5226777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ted Mann Theater |
E118009
|
entity |
| Predicate | hasScreeningType |
P9177
|
FINISHED |
| Object | premiere 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: premiere screenings | Statement: [Ted Mann Theater, hasScreeningType, premiere screenings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScreeningType Context triple: [Ted Mann Theater, hasScreeningType, premiere screenings]
-
A.
screeningType
chosen
Indicates the specific method or category of screening applied in a screening process or evaluation.
-
B.
hasScreened
Indicates that one entity has shown, displayed, or evaluated another entity, typically in the context of presenting media or conducting a review or check.
-
C.
hasSecurityScreening
Indicates that an entity is subject to, or has undergone, a security screening process.
-
D.
screeningOutcome
Indicates the result or decision produced by a screening or evaluation process applied to an entity.
-
E.
hasScreen
Indicates that an entity is equipped with or includes a screen or display component.
- 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_69bd4466fb8c819083b806a79414d7e4 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7addbdb88190baf9f47fc4cbb7fc |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77bd2a448190a9ae5afd2585a7b9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:48 p.m.