Triple

T35818265
Position Surface form Disambiguated ID Type / Status
Subject Kodak, Tennessee E1035427 entity
Predicate servedBy P82 FINISHED
Object Tennessee State Route 139
Tennessee State Route 139 is a state highway in eastern Tennessee that connects communities such as Kodak to nearby regional routes and destinations.
 E2160585 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: Tennessee State Route 139 | Statement: [Kodak, Tennessee, servedBy, Tennessee State Route 139]
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: Tennessee State Route 139
Triple: [Kodak, Tennessee, servedBy, Tennessee State Route 139]
Generated description
Tennessee State Route 139 is a state highway in eastern Tennessee that connects communities such as Kodak to nearby regional routes and destinations.

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_69f76e185ffc8190880b3cdf51decd38 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7a8fb5b20819084063d1797923342 completed May 3, 2026, 7:58 p.m.
NED1 Entity disambiguation (via context triple) batch_6a38a4dd462881909067994b24b9189c completed June 22, 2026, 2:58 a.m.
NEDg Description generation batch_6a38a8c5e7bc8190b05bd14a093c1b6c completed June 22, 2026, 3:15 a.m.
NED2 Entity disambiguation (via description) batch_6a38a91db08881908703647901730314 completed June 22, 2026, 3:16 a.m.
Created at: May 3, 2026, 4:06 p.m.