Triple
T2388864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Maine |
E48893
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Buxton, Maine |
E527093
|
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: Buxton, Maine | Statement: [Southern Maine, contains, Buxton, Maine]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Buxton, Maine Context triple: [Southern Maine, contains, Buxton, Maine]
-
A.
Buxton, Maine
chosen
Buxton, Maine is a small New England town in York County known for its rural character and proximity to the Portland metropolitan area.
-
B.
Benton, Maine
Benton, Maine is a small rural town in central Maine known for its agricultural character and location along the Kennebec River.
-
C.
Blaine, Maine
Blaine, Maine is a small rural town located in northeastern Maine near the Canadian border, within Aroostook County’s agricultural region.
-
D.
Bingham, Maine
Bingham, Maine is a small rural town in central Maine known for its outdoor recreation opportunities along the Kennebec River.
-
E.
Buckfield, Maine
Buckfield, Maine is a small rural town in western Maine known for its historic village center and location within Androscoggin 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_69a88aa5f63081908d07fd302029fcbd |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc7dca9248190b634ae9e02f6899a |
completed | March 7, 2026, 6:38 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c845c232188190a3391ce5159f49bb |
completed | March 28, 2026, 9:18 p.m. |
Created at: March 4, 2026, 7:57 p.m.