Triple
T5071996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British New Wave |
E114301
|
entity |
| Predicate | stylisticBreakFrom |
P21658
|
FINISHED |
| Object | traditional British studio melodrama |
—
|
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: traditional British studio melodrama | Statement: [British New Wave, stylisticBreakFrom, traditional British studio melodrama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stylisticBreakFrom Context triple: [British New Wave, stylisticBreakFrom, traditional British studio melodrama]
-
A.
breakType
Indicates the specific kind or category of break or interruption that occurs in a process, activity, or sequence.
-
B.
marksStylisticShiftFrom
chosen
Indicates that one element signals a change in style, tone, or manner relative to another element.
-
C.
breaksWith
Indicates that one entity ends or disrupts an existing association, agreement, or alignment with another entity.
-
D.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an entity.
-
E.
styleSegment
Indicates a relationship where one segment is characterized or defined by a particular style or formatting.
- 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_69bd443cf28c8190ad371d603563dbdd |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74ce140881909a2874663244c0db |
completed | March 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.