Triple

T9481068
Position Surface form Disambiguated ID Type / Status
Subject River Crouch E228637 entity
Predicate hasTributary P415 FINISHED
Object River Can E287817 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: River Can | Statement: [River Crouch, hasTributary, River Can]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Can
Context triple: [River Crouch, hasTributary, River Can]
  • A. River Can chosen
    River Can is a small river in Essex, England, that flows through the city of Chelmsford and forms part of the River Chelmer system.
  • B. El Caño
    El Caño is a pre-Columbian archaeological site in Panama known for its elaborate burial grounds and rich material remains associated with the Gran Coclé culture.
  • C. River Burn
    River Burn is a small river in Norfolk, England, known for flowing through the village of Burnham Thorpe near the north Norfolk coast.
  • D. River Burn
    River Burn is a small river in North Yorkshire, England, known for flowing through Wensleydale before joining the River Ure.
  • E. Rive
    Rive is a major public transport hub and urban square in central Geneva, Switzerland, serving as an important interchange point for buses and trolleybuses.
  • 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_69ca84730a5081908de282651019bf2f completed March 30, 2026, 2:10 p.m.
NER Named-entity recognition batch_69cd8018645c8190823d82a93635b345 completed April 1, 2026, 8:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69d12cfebb6c8190af3296c7bfd8b3e4 completed April 4, 2026, 3:23 p.m.
Created at: March 30, 2026, 7:54 p.m.