Triple
T13875264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 182 |
E333564
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Cherryfield, 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: Cherryfield, Maine | Statement: [Maine State Route 182, passesThrough, Cherryfield, Maine]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cherryfield, Maine Context triple: [Maine State Route 182, passesThrough, Cherryfield, Maine]
-
A.
Cherryfield, Maine
chosen
Cherryfield, Maine is a small town in Washington County known for its historic architecture and wild blueberry production.
-
B.
Montville, Maine
Montville, Maine is a small rural town in central Maine known for its forests, farms, and quiet, scenic countryside.
-
C.
Chapman, Maine
Chapman, Maine is a small rural town located in northern Maine within Aroostook County.
-
D.
Dixfield, Maine
Dixfield, Maine is a small New England town in western Maine known for its rural character and location along the Androscoggin River in Oxford County.
-
E.
Litchfield, Maine
Litchfield, Maine is a small rural town in central Maine known for its lakes, forests, and quiet residential character.
- 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_69d81c5ced9c8190b0e9bcc6effe5959 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0be556708190bbcf0b3583f677e3 |
completed | April 14, 2026, 9:41 a.m. |
Created at: April 9, 2026, 10:15 p.m.