Triple

T27339314
Position Surface form Disambiguated ID Type / Status
Subject Miles River E690047 entity
Predicate hasNearbySettlement P4647 FINISHED
Object Newcomb, Maryland
Newcomb, Maryland is a small unincorporated community in Talbot County on Maryland’s Eastern Shore, known for its rural waterfront setting along the Miles River.
E1905472 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: Newcomb, Maryland | Statement: [Miles River, hasNearbySettlement, Newcomb, Maryland]
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: Newcomb, Maryland
Triple: [Miles River, hasNearbySettlement, Newcomb, Maryland]
Generated description
Newcomb, Maryland is a small unincorporated community in Talbot County on Maryland’s Eastern Shore, known for its rural waterfront setting along the Miles River.

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_69ef355e5b388190a8fc1eba9b4a6656 completed April 27, 2026, 10:07 a.m.
NER Named-entity recognition batch_69f62ad17d30819082fd2c9dbc1f964f completed May 2, 2026, 4:48 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2764155a508190840fdf587bf36c4b completed June 9, 2026, 12:53 a.m.
NEDg Description generation batch_6a27652b29448190b6e9e9891ab878d3 completed June 9, 2026, 12:58 a.m.
NED2 Entity disambiguation (via description) batch_6a27661767f081909e0291186c5d6778 completed June 9, 2026, 1:02 a.m.
Created at: April 27, 2026, 11:42 a.m.