Triple

T8848598
Position Surface form Disambiguated ID Type / Status
Subject Pocomoke River E210574 entity
Predicate hasTributary P415 FINISHED
Object Nassawango Creek
Nassawango Creek is a scenic, ecologically rich waterway on the Delmarva Peninsula in Maryland, known for its extensive cypress swamps and protected natural areas.
E2297151 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: Nassawango Creek | Statement: [Pocomoke River, hasTributary, Nassawango 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: Nassawango Creek
Triple: [Pocomoke River, hasTributary, Nassawango Creek]
Generated description
Nassawango Creek is a scenic, ecologically rich waterway on the Delmarva Peninsula in Maryland, known for its extensive cypress swamps and protected natural areas.

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_69ca838a424c8190b1ecac115c2927e7 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc60aa6db0819097c3257499200afc completed April 1, 2026, 12:02 a.m.
NED1 Entity disambiguation (via context triple) batch_6a83174545388190b5a65efdcd3bb43c completed Aug. 17, 2026, 2:14 p.m.
NEDg Description generation batch_6a8317b186a8819093677ce312c19695 completed Aug. 17, 2026, 2:16 p.m.
NED2 Entity disambiguation (via description) batch_6a831db3bc80819098b0b6648aaef2f9 completed Aug. 17, 2026, 2:41 p.m.
Created at: March 30, 2026, 6:49 p.m.