Triple

T22638790
Position Surface form Disambiguated ID Type / Status
Subject Mad River (New Hampshire) E558760 entity
Predicate hasTributary P415 FINISHED
Object Flume Brook 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: Flume Brook | Statement: [Mad River (New Hampshire), hasTributary, Flume Brook]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Flume Brook
Context triple: [Mad River (New Hampshire), hasTributary, Flume Brook]
  • A. Flume Brook chosen
    Flume Brook is the mountain stream in New Hampshire’s White Mountains whose erosive power carved the dramatic granite chasm known as the Flume Gorge.
  • B. Henmore Brook
    Henmore Brook is a small watercourse in Derbyshire, England, that flows through the town of Ashbourne before joining the River Dove.
  • C. Childrey Brook
    Childrey Brook is a small stream in Oxfordshire, England, that flows through the village of Childrey and its surrounding countryside.
  • D. Naden Brook
    Naden Brook is a small river in Greater Manchester, England, that flows through the Pennine foothills before joining the River Roch.
  • E. Foudry Brook
    Foudry Brook is a small river in southern England that serves as a tributary within the River Loddon catchment.
  • 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_69e24547f7fc819086e2c4ba3b979657 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1700f9fac8190b82190a54be22413 completed April 29, 2026, 2:42 a.m.
Created at: April 17, 2026, 3:04 p.m.