Triple

T6490979
Position Surface form Disambiguated ID Type / Status
Subject River Esk E148034 entity
Predicate hasTributary P415 FINISHED
Object Great Fryup Beck E597627 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: Great Fryup Beck | Statement: [River Esk, hasTributary, Great Fryup Beck]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Great Fryup Beck
Context triple: [River Esk, hasTributary, Great Fryup Beck]
  • A. Skeeby Beck
    Skeeby Beck is a small stream in North Yorkshire, England, that serves as one of the tributaries feeding into the River Swale.
  • B. Cunsey Beck
    Cunsey Beck is a small river in the Lake District of England that drains Esthwaite Water and flows into the southern part of Windermere.
  • C. Trout Beck
    Trout Beck is a stream in the Lake District of Cumbria, England, that flows into the lake of Windermere.
  • D. Danby Beck chosen
    Danby Beck is a small stream in North Yorkshire, England, that flows through the Esk Valley as a tributary of the River Esk in the North York Moors.
  • E. River Cod Beck
    River Cod Beck is a small watercourse in North Yorkshire, England, that flows through the Hambleton district as part of the local river network.
  • 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_69c009088f3081909cd467b05919de30 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c06a9a8d8481908d88e5c9f0c773f7 completed March 22, 2026, 10:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69c669e216608190af64f8e61ddf0feb completed March 27, 2026, 11:28 a.m.
Created at: March 22, 2026, 4:53 p.m.