Triple
T6135510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forbidden Planet |
E136821
|
entity |
| Predicate | narrativeBasis |
P44225
|
FINISHED |
| Object | loose adaptation of The Tempest |
—
|
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: loose adaptation of The Tempest | Statement: [Forbidden Planet, narrativeBasis, loose adaptation of The Tempest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeBasis Context triple: [Forbidden Planet, narrativeBasis, loose adaptation of The Tempest]
-
A.
narrative
Indicates that one entity tells, presents, or conveys a story or sequence of events about another entity or situation.
-
B.
narrativeType
Indicates the specific kind or category of narrative (e.g., genre, structural form, or storytelling mode) associated with an entity.
-
C.
narrativeFrame
Indicates the overarching narrative context or perspective within which events, actions, or relationships are presented or interpreted.
-
D.
narrativePremise
chosen
Indicates the foundational situation, conflict, or setup that initiates and drives the narrative’s events.
-
E.
containsNarrativeOf
Indicates that one entity includes or presents the story, account, or narrative content of another entity.
- 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_69c008a179388190a3b5a081bbf46d55 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05c80a6088190a028967b682fed2b |
completed | March 22, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c055f19b0c81908be34a00ab218723 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:15 p.m.