Triple

T27045801
Position Surface form Disambiguated ID Type / Status
Subject Crawfish River E684621 entity
Predicate hasRightTributary P415 FINISHED
Object Maunesha River
The Maunesha River is a tributary waterway in south-central Wisconsin that flows through agricultural and rural landscapes before joining the Crawfish River.
E2293692 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: Maunesha River | Statement: [Crawfish River, hasRightTributary, Maunesha 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: Maunesha River
Triple: [Crawfish River, hasRightTributary, Maunesha River]
Generated description
The Maunesha River is a tributary waterway in south-central Wisconsin that flows through agricultural and rural landscapes before joining the Crawfish River.

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_69ef148193c48190bb1a0cfae6a407c4 completed April 27, 2026, 7:47 a.m.
NER Named-entity recognition batch_69f62270213c8190a6f991b6d4f3fbf6 completed May 2, 2026, 4:12 p.m.
NED1 Entity disambiguation (via context triple) batch_6a7af24f0244819081389ef96c43780c completed Aug. 11, 2026, 9:58 a.m.
NEDg Description generation batch_6a7af2a2676c819091ce1deb326fb497 completed Aug. 11, 2026, 10 a.m.
NED2 Entity disambiguation (via description) batch_6a7af36934888190904e448ca89eeace completed Aug. 11, 2026, 10:03 a.m.
Created at: April 27, 2026, 8:09 a.m.