Triple
T33781435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tape |
E865665
|
entity |
| Predicate | dramaticTensionSource |
P174943
|
FINISHED |
| Object | conflicting memories |
—
|
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: conflicting memories | Statement: [Tape, dramaticTensionSource, conflicting memories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dramaticTensionSource Context triple: [Tape, dramaticTensionSource, conflicting memories]
-
A.
tensionSource
chosen
Indicates that one entity is the origin or cause of tension affecting another entity or situation.
-
B.
dramaticSource
Indicates that something serves as the origin or basis for a dramatic work, performance, or representation.
-
C.
storyConflictSource
Indicates the source or cause from which a story’s central conflict arises.
-
D.
dramaticClimaxInvolvement
Indicates involvement in the pivotal, most intense turning point or climax of a dramatic work or narrative.
-
E.
tension
Indicates a state of strain, stress, or conflict existing between entities, often involving opposing forces, interests, or emotions.
- 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_69f3498ecc2c8190bcd85e3f11dc215e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:45 a.m.