Triple
T10089163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Storm Clouds Cantata |
E215296
|
entity |
| Predicate | reusedIn |
P91997
|
FINISHED |
| Object | remake of The Man Who Knew Too Much (1956 film) |
—
|
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: remake of The Man Who Knew Too Much (1956 film) | Statement: [Storm Clouds Cantata, reusedIn, remake of The Man Who Knew Too Much (1956 film)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reusedIn Context triple: [Storm Clouds Cantata, reusedIn, remake of The Man Who Knew Too Much (1956 film)]
-
A.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
B.
alsoUsedIn
Indicates that something is additionally employed, applied, or present in another context, setting, or use case beyond the primary one.
-
C.
notReusedFor
Indicates that something is not used again for a subsequent purpose, context, or instance.
-
D.
usedInPartOf
Indicates that something is utilized or plays a functional role within a specific component or subpart of a larger whole.
-
E.
laterRepurposedFor
Indicates that something was originally used for one purpose and subsequently assigned a different, new purpose.
- 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_69ca83a1eed081908b2e9580f2ebeea7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd057e32881908bf630559af94906 |
completed | April 2, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4b97870481908f7a89df10d58a9e |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 9:01 p.m.