Triple
T6503919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Power and the Glory (1933 film) |
E148957
|
entity |
| Predicate | screenplayStructure |
P30807
|
FINISHED |
| Object | flashback structure |
—
|
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: flashback structure | Statement: [The Power and the Glory (1933 film), screenplayStructure, flashback structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenplayStructure Context triple: [The Power and the Glory (1933 film), screenplayStructure, flashback structure]
-
A.
screenplayFocus
Indicates that a screenplay primarily centers on, highlights, or is chiefly concerned with a particular subject, character, or theme.
-
B.
coScreenwriter
Indicates that two or more individuals collaborated in writing the screenplay for the same work.
-
C.
screenplayType
chosen
Indicates the specific category or format of a screenplay associated with a work or production.
-
D.
screenplayBy
Indicates that a film, television show, or similar work was written or scripted by a particular person or group.
-
E.
screenplayRecord
Indicates that there exists a record or documentation associated with a particular screenplay, capturing information about its creation, version, or related details.
- 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_69c687e9ad288190bae5bcac9c8ac855 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f386aa08190bfc8592a92ec6339 |
completed | March 27, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69c68ab714908190aa7c2fbf64078e15 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:42 p.m.