Triple
T10888436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Fear (1991 film) |
E257111
|
entity |
| Predicate | containsReuseOf |
P91997
|
FINISHED |
| Object | Bernard Herrmann score themes |
—
|
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: Bernard Herrmann score themes | Statement: [Cape Fear (1991 film), containsReuseOf, Bernard Herrmann score themes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsReuseOf Context triple: [Cape Fear (1991 film), containsReuseOf, Bernard Herrmann score themes]
-
A.
reusedIn
chosen
Indicates that something previously used in one context or instance is used again in another context or instance.
-
B.
partiallyReusedAs
Indicates that one entity is used again as part of another entity, but only to a limited or incomplete extent rather than in its entirety.
-
C.
notReusedFor
Indicates that something is not used again for a subsequent purpose, context, or instance.
-
D.
containsReconstructionOf
Indicates that one entity includes or incorporates a recreated, restored, or reconstructed version of another entity.
-
E.
keyReuse
Indicates that the same key is used multiple times, rather than being uniquely generated or dedicated for a single use or context.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75202b7248190adeb5780fc5b9199 |
completed | April 9, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.