Triple

T3483411
Position Surface form Disambiguated ID Type / Status
Subject Hancock County, Maine E73548 entity
Predicate contains P35 FINISHED
Object Surry, Maine E494861 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: Surry, Maine | Statement: [Hancock County, Maine, contains, Surry, Maine]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Surry, Maine
Context triple: [Hancock County, Maine, contains, Surry, Maine]
  • A. Lovell, Maine
    Lovell, Maine is a small rural town in Oxford County known for its scenic lakes and mountains in western Maine.
  • B. Monmouth, Maine
    Monmouth, Maine is a small rural town in central Maine known for its lakes, agricultural heritage, and proximity to the state capital region.
  • C. Shapleigh, Maine
    Shapleigh, Maine is a small rural town in southwestern Maine known for its forests, lakes, and outdoor recreation.
  • D. Ellsworth, Maine chosen
    Ellsworth, Maine is a small city in Hancock County that serves as a commercial hub and gateway to the Downeast region and nearby Acadia National Park.
  • E. Porter, Maine
    Porter, Maine is a small rural town in Oxford County known for its scenic setting near the New Hampshire border and its traditional New England character.
  • 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_69ad85b3c9b08190857cae74c7f36da9 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adbb781e9c8190810fdd814f506127 completed March 8, 2026, 6:10 p.m.
NED1 Entity disambiguation (via context triple) batch_69d20c75bf508190a812c87950cb5227 completed April 5, 2026, 7:17 a.m.
Created at: March 8, 2026, 3:17 p.m.