Triple

T961780
Position Surface form Disambiguated ID Type / Status
Subject Hunter Valley E20749 entity
Predicate contains P35 FINISHED
Object Cessnock E81928 NE 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: Cessnock | Statement: [Hunter Valley, contains, Cessnock]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cessnock
Context triple: [Hunter Valley, contains, Cessnock]
  • A. Cessnock chosen
    Cessnock is a city in New South Wales, Australia, known as a gateway to the Hunter Valley wine region.
  • B. Peaslake
    Peaslake is a small rural village in Surrey, England, known for its scenic woodland surroundings and popularity with walkers and mountain bikers.
  • C. Wylam
    Wylam is a village in Northumberland, England, historically notable as the birthplace of pioneering railway engineer George Stephenson.
  • D. Shanklin
    Shanklin is a popular seaside resort town on the Isle of Wight in England, known for its sandy beach, Victorian architecture, and scenic coastal walks.
  • E. Hythe
    Hythe is a historic coastal town in Kent, England, known as one of the original Cinque Ports that once played a key role in maritime defense and trade.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69a493b21f2881908132dcf45dcd2f36 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b415ac688190bbcef455935a3116 completed March 1, 2026, 9:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac25845f588190b0f60754636a88d0 completed March 7, 2026, 1:17 p.m.
Created at: March 1, 2026, 7:40 p.m.