Triple

T10509105
Position Surface form Disambiguated ID Type / Status
Subject Messalonskee Lake E247864 entity
Predicate locatedNear P294 FINISHED
Object Belgrade, Maine E403110 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: Belgrade, Maine | Statement: [Messalonskee Lake, locatedNear, Belgrade, Maine]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Belgrade, Maine
Context triple: [Messalonskee Lake, locatedNear, Belgrade, Maine]
  • A. Belgrade, Maine chosen
    Belgrade, Maine is a small town in central Maine known for its scenic chain of lakes and rural New England character.
  • B. Trenton, Maine
    Trenton, Maine is a small coastal town in Hancock County that serves as a gateway to Mount Desert Island and Acadia National Park.
  • C. Dresden, Maine
    Dresden, Maine is a small rural town in Lincoln County known for its historic character and scenic location along the Kennebec River.
  • D. Frankfort, Maine
    Frankfort, Maine is a small rural town in Waldo County known for its scenic setting along the Penobscot River and its historic New England character.
  • E. Oakland, Maine
    Oakland, Maine is a small town in central Maine known for its lakeside setting, residential character, and proximity to the city of Waterville.
  • 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_69d381c4aa948190942e1d803143fb0e completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d509b359ac8190b3683cc6b9c70a71 completed April 7, 2026, 1:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69fee5da6a2081909dcc9785598e1196 completed May 9, 2026, 7:44 a.m.
Created at: April 6, 2026, 12:26 p.m.