Triple

T14933003
Position Surface form Disambiguated ID Type / Status
Subject Maine State Route 201 E372315 entity
Predicate passesThrough P225 FINISHED
Object Richmond, Maine
Richmond, Maine is a small town in Sagadahoc County known for its historic village center and location along the Kennebec River in central coastal Maine.
E1735870 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: Richmond, Maine | Statement: [Maine State Route 201, passesThrough, Richmond, 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: Richmond, Maine
Triple: [Maine State Route 201, passesThrough, Richmond, Maine]
Generated description
Richmond, Maine is a small town in Sagadahoc County known for its historic village center and location along the Kennebec River in central coastal Maine.

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_69d85cc9da0c81908d583ca3f63a3908 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded646a0808190ba5c0c91bde011c5 completed April 15, 2026, 12:05 a.m.
NED1 Entity disambiguation (via context triple) batch_6a11ebe189408190a1aa02b093912dcb completed May 23, 2026, 6:03 p.m.
NEDg Description generation batch_6a11ef2bf6fc81908c9073c3deca6ebf completed May 23, 2026, 6:17 p.m.
NED2 Entity disambiguation (via description) batch_6a11ef8994048190aca5d61de927d20c completed May 23, 2026, 6:18 p.m.
Created at: April 10, 2026, 2:37 a.m.