Triple

T35112602
Position Surface form Disambiguated ID Type / Status
Subject George Melbury E1013334 entity
Predicate centralConflictDriverIn P5022 FINISHED
Object The Woodlanders NE NERFINISHED

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: The Woodlanders | Statement: [George Melbury, centralConflictDriverIn, The Woodlanders]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: centralConflictDriverIn
Context triple: [George Melbury, centralConflictDriverIn, The Woodlanders]
  • A. centralConflictIn
    Indicates that one situation, issue, or opposition serves as the primary source of tension or struggle within another context, such as a story, event, or scenario.
  • B. centralIn
    Indicates that one entity occupies a central or most important position within another entity, context, or structure.
  • C. mainConflict chosen
    Indicates the primary opposing force, problem, or struggle that drives tension and narrative progression between entities or sides.
  • D. internalConflict
    Indicates a relationship where an entity experiences opposing desires, beliefs, or motives within itself, leading to psychological or emotional tension.
  • E. centralWork
    Indicates that a particular work is the primary, most important, or focal work associated with an entity 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_69f76dd659d08190bcdc00d37caafb62 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fd8ccbd4c88190b13aae0673b3c821 completed May 8, 2026, 7:12 a.m.
PD Predicate disambiguation batch_69fd8ae2227c819089546f5c3629799e completed May 8, 2026, 7:04 a.m.
Created at: May 3, 2026, 4:01 p.m.