Triple

T11873202
Position Surface form Disambiguated ID Type / Status
Subject Lambourn Brook E282454 entity
Predicate hasName P744 FINISHED
Object Lambourn Brook E421534 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: Lambourn Brook | Statement: [Lambourn Brook, hasName, Lambourn Brook]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lambourn Brook
Context triple: [Lambourn Brook, hasName, Lambourn Brook]
  • A. Lambourn Brook chosen
    Lambourn Brook is a small river in southern England that flows through the village of Lambourn before joining the River Windrush.
  • B. Bourn Brook
    Bourn Brook is a small watercourse in Birmingham, England, that flows through urban and suburban areas before joining the River Rea.
  • C. Letcombe Brook
    Letcombe Brook is a small chalk stream in Oxfordshire, England, valued for its clear waters, rich wildlife, and role in the local landscape around Wantage.
  • D. Rothley Brook
    Rothley Brook is a small river in Leicestershire, England, that flows through rural and suburban areas before joining the River Soar.
  • E. Shuttleworth Brook
    Shuttleworth Brook is a small watercourse in Lancashire, England, that serves as a minor tributary within the River Calder catchment.
  • 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_69d6ab2945d081908a5851c916cbcfb5 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8be18b7d48190b7fb1c3a67a891ed completed April 10, 2026, 9:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69f4716d92c881908d45cb7b3babb1f7 completed May 1, 2026, 9:25 a.m.
Created at: April 8, 2026, 9:43 p.m.