Triple

T7843700
Position Surface form Disambiguated ID Type / Status
Subject River Coquet E181866 entity
Predicate flowsThrough P225 FINISHED
Object Holystone E679395 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: Holystone | Statement: [River Coquet, flowsThrough, Holystone]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Holystone
Context triple: [River Coquet, flowsThrough, Holystone]
  • A. Holystone chosen
    Holystone is a small historic village in Northumberland, England, known for its scenic rural setting and ancient religious sites.
  • B. Bygrave
    Bygrave is a small rural village in the North Hertfordshire district of Hertfordshire, England, known for its historic church and surrounding farmland.
  • C. Blackwall
    Blackwall is a coastal suburb on the Central Coast of New South Wales, Australia, known for its residential character and proximity to Brisbane Water.
  • D. Blackwall
    Blackwall is a historic riverside district in East London, known for its maritime heritage and former docklands along the River Thames.
  • E. Grindon
    Grindon is a residential suburb of Sunderland in the Wearside area of North East England.
  • 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_69ca8285d6488190a95d4c02d7354b53 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb163c72248190b53bc53980e8ac0f completed March 31, 2026, 12:33 a.m.
NED1 Entity disambiguation (via context triple) batch_69cb5ae9758c819091e270343ed289aa completed March 31, 2026, 5:26 a.m.
Created at: March 30, 2026, 4:48 p.m.