Triple
T11926888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kennebec River watershed |
E283805
|
entity |
| Predicate | containsTown |
P847
|
FINISHED |
| Object | Solon, Maine |
—
|
NE NERFINISHED |
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: Solon, Maine | Statement: [Kennebec River watershed, containsTown, Solon, Maine]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Solon, Maine Context triple: [Kennebec River watershed, containsTown, Solon, Maine]
-
A.
Solon, Maine
chosen
Solon, Maine is a small rural town in central Maine known for its scenic Kennebec River setting and outdoor recreation opportunities.
-
B.
Lovell, Maine
Lovell, Maine is a small rural town in Oxford County known for its scenic lakes and mountains in western Maine.
-
C.
Wells, Maine
Wells, Maine is a historic coastal town in southern Maine known for its long sandy beaches and role as a popular summer vacation destination.
-
D.
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.
-
E.
Thorndike, Maine
Thorndike, Maine is a small rural town located in Waldo County in the central part of the state.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8e3ff308190851ce656286bc67e |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 8, 2026, 9:45 p.m.