Triple

T13949131
Position Surface form Disambiguated ID Type / Status
Subject River Gade E335471 entity
Predicate flowsThrough P225 FINISHED
Object Apsley E211895 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: Apsley | Statement: [River Gade, flowsThrough, Apsley]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Apsley
Context triple: [River Gade, flowsThrough, Apsley]
  • A. Apsley chosen
    Apsley is a suburban village and residential area within the town of Hemel Hempstead in Hertfordshire, England, known for its canal-side setting and former paper mills.
  • B. Poppleton
    Poppleton is a village and civil parish in North Yorkshire, England, situated just west of York and known for its historic character and commuter links.
  • C. Aspley Guise
    Aspley Guise is a village and civil parish in Bedfordshire, England, known for its historic architecture and affluent residential character.
  • D. Austerfield
    Austerfield is a small village in South Yorkshire, England, notable for its historic church and connections to early English history.
  • E. Highworth
    Highworth is a historic market town in Wiltshire, England, known for its elevated position and traditional architecture.
  • 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_69d81c6081b88190b53e317c3370c8fe completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2e12171c8190b95746bdd4845def completed April 14, 2026, 12:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7ce917b7881908e1916fe2c597fe4 completed May 3, 2026, 10:39 p.m.
Created at: April 9, 2026, 10:17 p.m.