Triple

T3087783
Position Surface form Disambiguated ID Type / Status
Subject Poland, Maine E64413 entity
Predicate bordersTown P224 FINISHED
Object Raymond, Maine E445719 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: Raymond, Maine | Statement: [Poland, Maine, bordersTown, Raymond, Maine]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Raymond, Maine
Context triple: [Poland, Maine, bordersTown, Raymond, Maine]
  • A. Raymond, Maine chosen
    Raymond, Maine is a small lakeside town in southern Maine known for its scenic beauty, outdoor recreation, and proximity to the Portland metropolitan area.
  • B. Blaine, Maine
    Blaine, Maine is a small rural town located in northeastern Maine near the Canadian border, within Aroostook County’s agricultural region.
  • C. Lovell, Maine
    Lovell, Maine is a small rural town in Oxford County known for its scenic lakes and mountains in western Maine.
  • D. Veazie, Maine
    Veazie, Maine is a small residential town in eastern Maine located along the Penobscot River near the city of Bangor.
  • 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_69ad857c97d88190b26f9b1c90839c77 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada437c5e08190af22f6fa11cf9252 completed March 8, 2026, 4:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69ca1b0bc2108190bdb3915c0fd94ff1 completed March 30, 2026, 6:41 a.m.
Created at: March 8, 2026, 3:03 p.m.