Triple
T10357416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 135 |
E244033
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Litchfield, Maine |
E421172
|
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: Litchfield, Maine | Statement: [Maine State Route 135, passesThrough, Litchfield, Maine]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Litchfield, Maine Context triple: [Maine State Route 135, passesThrough, Litchfield, Maine]
-
A.
Litchfield, Maine
chosen
Litchfield, Maine is a small rural town in central Maine known for its lakes, forests, and quiet residential character.
-
B.
Buckfield, Maine
Buckfield, Maine is a small rural town in western Maine known for its historic village center and location within Androscoggin County.
-
C.
Greenfield, Maine
Greenfield, Maine is a small rural town located in Penobscot County in the central part of the state.
-
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.
Windham, Maine
Windham, Maine is a suburban town in southern Maine known for its proximity to Portland and its lakeside recreation areas.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9563ea48190b8702b3ef497ed9a |
completed | April 7, 2026, 11:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fda8fd6f5081908de9a9e3df28a8ea |
completed | May 8, 2026, 9:12 a.m. |
Created at: April 6, 2026, 11:58 a.m.