Triple

T21388978
Position Surface form Disambiguated ID Type / Status
Subject Hampton Court Way E527586 entity
Predicate crosses P416 FINISHED
Object River Ember 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: River Ember | Statement: [Hampton Court Way, crosses, River Ember]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Ember
Context triple: [Hampton Court Way, crosses, River Ember]
  • A. River Ember chosen
    The River Ember is a small watercourse in Surrey, England, that branches from and later rejoins the River Mole before flowing toward the River Thames.
  • B. River Ash
    River Ash is a small river in Hertfordshire, England, that flows through villages such as Little Hadham before joining the River Lea.
  • C. River Scar
    River Scar is a small tributary watercourse in Scotland that feeds into the River Nith within its wider river system.
  • D. River Mur
    The River Mur is a major Central European river that flows through Austria, Slovenia, and Croatia before joining the Drava.
  • E. Mother River
    Mother River is the local name for the Mo Chhu, a significant river in Bhutan known for its scenic valleys and cultural importance.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b51ff3748190935c0a513c62a12b completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69ee62cbfef08190a33ac1f198c82cd0 completed April 26, 2026, 7:09 p.m.
Created at: April 16, 2026, 5:12 p.m.