Triple

T21352677
Position Surface form Disambiguated ID Type / Status
Subject Maine State Route 32 E526528 entity
Predicate connectsCommunity P12608 FINISHED
Object Waldoboro, Maine
Waldoboro, Maine is a small coastal town in Lincoln County known for its historic shipbuilding heritage and scenic location along the Medomak River.
E2289258 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: Waldoboro, Maine | Statement: [Maine State Route 32, connectsCommunity, Waldoboro, Maine]
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: Waldoboro, Maine
Triple: [Maine State Route 32, connectsCommunity, Waldoboro, Maine]
Generated description
Waldoboro, Maine is a small coastal town in Lincoln County known for its historic shipbuilding heritage and scenic location along the Medomak 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_69e0b51cd5cc81909ac1187971e8a8ad completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e8ad34a1d48190b14fa099968faf7c completed April 22, 2026, 11:12 a.m.
NED1 Entity disambiguation (via context triple) batch_6a5b184e3df081909ef14d079416a416 completed July 18, 2026, 6:08 a.m.
NEDg Description generation batch_6a5b18b5ed9081909c1f63bfe986b26c completed July 18, 2026, 6:09 a.m.
NED2 Entity disambiguation (via description) batch_6a5b19177aac8190ad7e5adf724fb089 completed July 18, 2026, 6:11 a.m.
Created at: April 16, 2026, 5:05 p.m.