Triple
T536571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aroostook County, Maine |
E12339
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Littleton, Maine |
E240441
|
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: Littleton, Maine | Statement: [Aroostook County, Maine, hasTown, Littleton, Maine]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Littleton, Maine Context triple: [Aroostook County, Maine, hasTown, Littleton, Maine]
-
A.
Wilton, Maine
Wilton, Maine is a small New England town known for its scenic lakes, outdoor recreation, and historic mill heritage.
-
B.
Mapleton, Maine
chosen
Mapleton, Maine is a small rural town in northern Maine known for its agricultural landscape and location within Aroostook County.
-
C.
Woodville, Maine
Woodville, Maine is a small rural town located in Penobscot County in the central part of the state.
-
D.
Newburgh, Maine
Newburgh, Maine is a small rural town in central Maine known for its agricultural character and quiet residential community.
-
E.
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.
- 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a496da8e108190b4874c3b85290464 |
completed | March 1, 2026, 7:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af5ca0ede48190b2c45761a3f92517 |
completed | March 9, 2026, 11:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.