Triple

T16129391
Position Surface form Disambiguated ID Type / Status
Subject Red Brook E391353 entity
Predicate hasName P744 FINISHED
Object Red 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: Red Brook | Statement: [Red Brook, hasName, Red Brook]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Red Brook
Context triple: [Red Brook, hasName, Red Brook]
  • A. Red Brook chosen
    Red Brook is a natural watercourse and wildlife habitat in the Partington area, valued as a local site for nature and outdoor recreation.
  • B. Trout Brook
    Trout Brook is a tributary stream that forms part of the Park River watershed in Connecticut.
  • C. Salmon Brook
    Salmon Brook is a small tributary stream in north London, England, that flows through suburban areas before joining the River Lea.
  • D. Indian Brook
    Indian Brook is a small river in Essex, Vermont, known locally for its surrounding natural areas and recreational opportunities.
  • E. Franconia Brook
    Franconia Brook is a mountain stream in New Hampshire’s White Mountains that flows through the remote Pemigewasset Wilderness, popular with hikers and backcountry campers.
  • 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_69d87f1bb0988190b490d273dbf3fd03 completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e202075860819088d27d921609a6ce completed April 17, 2026, 9:48 a.m.
Created at: April 10, 2026, 5:01 a.m.