Triple

T2359846
Position Surface form Disambiguated ID Type / Status
Subject St. John Valley E47245 entity
Predicate majorTown P316 FINISHED
Object Fort Kent, Maine E6034 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: Fort Kent, Maine | Statement: [St. John Valley, majorTown, Fort Kent, Maine]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fort Kent, Maine
Context triple: [St. John Valley, majorTown, Fort Kent, Maine]
  • A. Fort Kent, Maine chosen
    Fort Kent, Maine is a small town in northern Aroostook County known for its location at the Canadian border and as a gateway to the North Maine Woods.
  • B. Mapleton, Maine
    Mapleton, Maine is a small rural town in northern Maine known for its agricultural landscape and location within Aroostook County.
  • C. Stetson, Maine
    Stetson, Maine is a small rural town in central Maine known for its lakes, forests, and quiet residential character.
  • D. Dixfield, Maine
    Dixfield, Maine is a small New England town in western Maine known for its rural character and location along the Androscoggin River in Oxford County.
  • E. Newburgh, Maine
    Newburgh, Maine is a small rural town in central Maine known for its agricultural character and quiet residential community.
  • 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_69a88a1a4a6081908645b0f2914521ab completed March 4, 2026, 7:38 p.m.
NER Named-entity recognition batch_69abc722ac3c819091f4316a4a166a77 completed March 7, 2026, 6:35 a.m.
NED1 Entity disambiguation (via context triple) batch_69b2e803e994819085dae09224fae2a3 completed March 12, 2026, 4:21 p.m.
Created at: March 4, 2026, 7:55 p.m.