Triple

T21740041
Position Surface form Disambiguated ID Type / Status
Subject Wellsburg, West Virginia E536630 entity
Predicate hasTransportation P105 FINISHED
Object Wellsburg Bridge
Wellsburg Bridge is a modern Ohio River crossing that connects Wellsburg, West Virginia, with Brilliant, Ohio, improving regional transportation and traffic flow.
E1608747 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: Wellsburg Bridge | Statement: [Wellsburg, West Virginia, hasTransportation, Wellsburg 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: Wellsburg Bridge
Triple: [Wellsburg, West Virginia, hasTransportation, Wellsburg Bridge]
Generated description
Wellsburg Bridge is a modern Ohio River crossing that connects Wellsburg, West Virginia, with Brilliant, Ohio, improving regional transportation and traffic flow.

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_69e0c46df5448190b4322127ffc4c690 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f01a714c208190b96efe23ed3bf0db completed April 28, 2026, 2:24 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0f75df2518819085c5f0dc001de791 completed May 21, 2026, 9:15 p.m.
NEDg Description generation batch_6a0f76f167d08190a9e4d3abc3cc4545 completed May 21, 2026, 9:19 p.m.
NED2 Entity disambiguation (via description) batch_6a0f78c5e978819086792ca6d9835ff9 completed May 21, 2026, 9:27 p.m.
Created at: April 16, 2026, 6:49 p.m.