Triple

T30976227
Position Surface form Disambiguated ID Type / Status
Subject Mosby Creek Covered Bridge E789239 entity
Predicate crosses P416 FINISHED
Object Mosby Creek
Mosby Creek is a stream in Oregon known for being spanned by the historic Mosby Creek Covered Bridge.
E2295239 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: Mosby Creek | Statement: [Mosby Creek Covered Bridge, crosses, Mosby 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: Mosby Creek
Triple: [Mosby Creek Covered Bridge, crosses, Mosby Creek]
Generated description
Mosby Creek is a stream in Oregon known for being spanned by the historic Mosby Creek Covered Bridge.

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_69f224c4831c8190be53924ec25a150a completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f693b92cb48190b1f354d3ca38375c completed May 3, 2026, 12:15 a.m.
NED1 Entity disambiguation (via context triple) batch_6a7d2536fb608190b818a64bc5439c20 completed Aug. 13, 2026, 2 a.m.
NEDg Description generation batch_6a7d2609ec08819081c921b02185dc05 completed Aug. 13, 2026, 2:03 a.m.
NED2 Entity disambiguation (via description) batch_6a7d26608d68819093fa0372d05264a3 completed Aug. 13, 2026, 2:05 a.m.
Created at: April 29, 2026, 8:55 p.m.