Triple

T25268976
Position Surface form Disambiguated ID Type / Status
Subject Jellico, Tennessee E633511 entity
Predicate locatedOn P40 FINISHED
Object Jellico Creek
Jellico Creek is a stream in Tennessee known for running through the town of Jellico and contributing to the region’s local watershed.
E2289840 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: Jellico Creek | Statement: [Jellico, Tennessee, locatedOn, Jellico Creek]
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: Jellico Creek
Triple: [Jellico, Tennessee, locatedOn, Jellico Creek]
Generated description
Jellico Creek is a stream in Tennessee known for running through the town of Jellico and contributing to the region’s local 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_69e75a92f48881909974ff9c11150a2e completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f48ba023b481908b6c6caf212818a3 completed May 1, 2026, 11:16 a.m.
NED1 Entity disambiguation (via context triple) batch_6a5b72abd76c81908362db460bc90639 completed July 18, 2026, 12:33 p.m.
NEDg Description generation batch_6a5b73146f808190a113ee0b8947ee44 completed July 18, 2026, 12:35 p.m.
NED2 Entity disambiguation (via description) batch_6a5b73bd0ba081909c96f74abc00eb9c completed July 18, 2026, 12:38 p.m.
Created at: April 21, 2026, 1:16 p.m.