Triple
T4447053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resurrection (1912 film) |
E96313
|
entity |
| Predicate | usesIntertitles |
P17467
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Resurrection (1912 film), usesIntertitles, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesIntertitles Context triple: [Resurrection (1912 film), usesIntertitles, true]
-
A.
hasIntertitlesLanguage
Indicates that the intertitles of a film or audiovisual work are presented in a specified language.
-
B.
silentWithIntertitles
chosen
Indicates that a work is a silent production that conveys dialogue or narrative information through intertitles rather than synchronized spoken sound.
-
C.
hasSubtitles
Indicates that one media item provides subtitle text or tracks that accompany another media item or its audio content.
-
D.
containsInterludes
Indicates that one entity (typically a work or composition) includes one or more interludes within its structure.
-
E.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
- 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355d31e10819086590b9f828d50b0 |
completed | March 13, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69b34f62c180819097ced38da2052207 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:32 p.m.