Triple
T10566803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 137 |
E249370
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Searsmont, Maine |
E849103
|
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: Searsmont, Maine | Statement: [Maine State Route 137, connects, Searsmont, Maine]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Searsmont, Maine Context triple: [Maine State Route 137, connects, Searsmont, Maine]
-
A.
Searsmont, Maine
chosen
Searsmont, Maine is a small rural town in Waldo County known for its forests, lakes, and traditional New England character.
-
B.
Shapleigh, Maine
Shapleigh, Maine is a small rural town in southwestern Maine known for its forests, lakes, and outdoor recreation.
-
C.
St. George, Maine
St. George, Maine is a small coastal town in the Midcoast region of Maine known for its fishing heritage, scenic peninsulas, and views of the Atlantic Ocean.
-
D.
Rockwood, Maine
Rockwood, Maine is a small unincorporated community and popular outdoor recreation gateway on the western shore of Moosehead Lake in north-central Maine.
-
E.
Ripley, Maine
Ripley, Maine is a small rural town located in Somerset County in central Maine.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5272ef5848190b76d671ea2d26314 |
completed | April 7, 2026, 3:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff2ce12e78819080b3fe19c57ef3ef |
completed | May 9, 2026, 12:47 p.m. |
Created at: April 6, 2026, 12:36 p.m.