Triple

T3074833
Position Surface form Disambiguated ID Type / Status
Subject Standish, Maine E64111 entity
Predicate adjacentTo P224 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: [Standish, Maine, adjacentTo, Buxton, Maine]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Buxton, Maine
Context triple: [Standish, Maine, adjacentTo, 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_69ad857a8aec8190bfdfd9c14554ac5a completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada14f5ee0819097ae04b3163dd954 completed March 8, 2026, 4:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69c9d13a8b108190a0b13592f3a6362e completed March 30, 2026, 1:26 a.m.
Created at: March 8, 2026, 3:02 p.m.