Triple

T15083475
Position Surface form Disambiguated ID Type / Status
Subject Brunswick, Maine E360208 entity
Predicate adjacentTo P224 FINISHED
Object Bath, 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: Bath, Maine | Statement: [Brunswick, Maine, adjacentTo, Bath, Maine]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bath, Maine
Context triple: [Brunswick, Maine, adjacentTo, Bath, Maine]
  • A. Bath, Maine chosen
    Bath, Maine is a small coastal city on the Kennebec River known for its historic shipbuilding industry and home to the major naval shipyard Bath Iron Works.
  • B. West Bath, Maine
    West Bath, Maine is a small coastal town in Sagadahoc County known for its rural character and proximity to the Kennebec River and Midcoast region.
  • C. Waterford, Maine
    Waterford, Maine is a small rural town in Oxford County known for its lakes, forests, and traditional New England village character.
  • D. Blaine, Maine
    Blaine, Maine is a small rural town located in northeastern Maine near the Canadian border, within Aroostook County’s agricultural region.
  • E. Burnham, Maine
    Burnham, 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_69d85a035aa88190b52a139d3a1b7b6d completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0027450a48190a84588b6aaf84ebf completed April 15, 2026, 9:26 p.m.
Created at: April 10, 2026, 3:03 a.m.