Triple

T34927987
Position Surface form Disambiguated ID Type / Status
Subject White River (Vermont) E1007344 entity
Predicate hasTributary P415 FINISHED
Object West Branch White River
West Branch White River is a tributary stream in Vermont that feeds into the White River, contributing to the Connecticut River watershed.
E2126564 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: West Branch White River | Statement: [White River (Vermont), hasTributary, West Branch White River]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: West Branch White River
Triple: [White River (Vermont), hasTributary, West Branch White River]
Generated description
West Branch White River is a tributary stream in Vermont that feeds into the White River, contributing to the Connecticut River watershed.

Provenance (5 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_69f76dc3d83881909d5c3c14455cfa2c completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f7825301b8819098c6e1382c2254a1 completed May 3, 2026, 5:13 p.m.
NED1 Entity disambiguation (via context triple) batch_6a37cfd585e08190b37d0358d029aa24 completed June 21, 2026, 11:49 a.m.
NEDg Description generation batch_6a37d13265808190bd6e411f0cdc7935 completed June 21, 2026, 11:55 a.m.
NED2 Entity disambiguation (via description) batch_6a37d2c3f87481909cee73b672325b1f completed June 21, 2026, 12:02 p.m.
Created at: May 3, 2026, 4 p.m.