Triple
T3460245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planet Terror |
E73005
|
entity |
| Predicate | screenedAs |
P28181
|
FINISHED |
| Object | part of Grindhouse double feature in theaters |
—
|
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: part of Grindhouse double feature in theaters | Statement: [Planet Terror, screenedAs, part of Grindhouse double feature in theaters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenedAs Context triple: [Planet Terror, screenedAs, part of Grindhouse double feature in theaters]
-
A.
hasScreened
chosen
Indicates that one entity has shown, displayed, or evaluated another entity, typically in the context of presenting media or conducting a review or check.
-
B.
screeningType
Indicates the specific method or category of screening applied in a screening process or evaluation.
-
C.
hasSecurityScreening
Indicates that an entity is subject to, or has undergone, a security screening process.
-
D.
firstScreeningLocation
Indicates the location where something (such as a person, item, or case) is initially screened or evaluated for the first time.
-
E.
firstScreeningEvent
Indicates the event representing the earliest or initial screening occurrence associated with an entity.
- 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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbae5ff848190880fa416a123bc4a |
completed | March 8, 2026, 6:07 p.m. |
| PD | Predicate disambiguation | batch_69adae05bb0081909dc7e4779d6e05ef |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.