Triple

T38458865
Position Surface form Disambiguated ID Type / Status
Subject Kentucky–Indiana region E912393 entity
Predicate hasBridge P386 FINISHED
Object Lewis and Clark Bridge
The Lewis and Clark Bridge is a major Ohio River crossing that connects Kentucky and Indiana as part of the Louisville metropolitan area’s highway network.
E2284587 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: Lewis and Clark Bridge | Statement: [Kentucky–Indiana region, hasBridge, Lewis and Clark Bridge]
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: Lewis and Clark Bridge
Triple: [Kentucky–Indiana region, hasBridge, Lewis and Clark Bridge]
Generated description
The Lewis and Clark Bridge is a major Ohio River crossing that connects Kentucky and Indiana as part of the Louisville metropolitan area’s highway network.

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_69f76e84e2dc81908badf05b3aafa9ea completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fcce05064c8190828685e79f32db3c completed May 7, 2026, 5:38 p.m.
NED1 Entity disambiguation (via context triple) batch_6a43d704f11c8190be7e285d501c4dc2 completed June 30, 2026, 2:47 p.m.
NEDg Description generation batch_6a43d8657b3481908169f3baa75cbabf completed June 30, 2026, 2:53 p.m.
NED2 Entity disambiguation (via description) batch_6a43dc1dc6e08190ad5596a14b51f254 completed June 30, 2026, 3:09 p.m.
Created at: May 3, 2026, 4:31 p.m.