Triple
T2894793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific Theatres |
E63909
|
entity |
| Predicate | closureAffected |
P43844
|
FINISHED |
| Object | Cinerama Dome operations |
—
|
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: Cinerama Dome operations | Statement: [Pacific Theatres, closureAffected, Cinerama Dome operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closureAffected Context triple: [Pacific Theatres, closureAffected, Cinerama Dome operations]
-
A.
closureContext
Indicates the surrounding scope or environment in which an operation, expression, or function is defined and executed, capturing the variables and bindings available to it.
-
B.
closureFrequency
Indicates how often a particular process, event, or entity is closed or brought to an end within a given period.
-
C.
closureThreshold
Indicates the limit or boundary value at which a process, operation, or state is considered complete or closed.
-
D.
closureAnnouncedBy
Indicates that an entity’s closure has been formally communicated or declared by a specified agent or source.
-
E.
subjectToClosure
Indicates that an entity is liable or scheduled to be closed, discontinued, or shut down under certain conditions or plans.
- 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_69ab4c45822c8190830c5f2bb97bcfd0 |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe063de6c8190bce9ddefd1dd62e1 |
completed | March 7, 2026, 8:23 a.m. |
| PD | Predicate disambiguation | batch_69abdd17bcdc8190aa47274a50ba4ad4 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde0f4c648190b9812e64f30c39da |
completed | March 7, 2026, 8:13 a.m. |
Created at: March 6, 2026, 10:07 p.m.