Triple

T38549504
Position Surface form Disambiguated ID Type / Status
Subject Green River basin E925067 entity
Predicate containsTributary P415 FINISHED
Object Little Barren River
The Little Barren River is a tributary waterway in south-central Kentucky that feeds into the Green River system and drains a largely rural, agricultural region.
E2279250 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: Little Barren River | Statement: [Green River basin, containsTributary, Little Barren 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: Little Barren River
Triple: [Green River basin, containsTributary, Little Barren River]
Generated description
The Little Barren River is a tributary waterway in south-central Kentucky that feeds into the Green River system and drains a largely rural, agricultural region.

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_69f76eaeb69c8190b367df9330d6f6af completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fcd3163d0881909d3209cd7cb81c10 completed May 7, 2026, 5:59 p.m.
NED1 Entity disambiguation (via context triple) batch_6a41fd4ae44881908363c1826e586564 completed June 29, 2026, 5:06 a.m.
NEDg Description generation batch_6a41fe5538388190928844feec401ee0 completed June 29, 2026, 5:10 a.m.
NED2 Entity disambiguation (via description) batch_6a41fec71d2881908cf49cf62cc129c6 completed June 29, 2026, 5:12 a.m.
Created at: May 3, 2026, 4:32 p.m.