Triple

T12779722
Position Surface form Disambiguated ID Type / Status
Subject Maine State Route 168 E305473 entity
Predicate connects P390 FINISHED
Object Lee, 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: Lee, Maine | Statement: [Maine State Route 168, connects, Lee, Maine]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lee, Maine
Context triple: [Maine State Route 168, connects, Lee, Maine]
  • A. Lee, Maine chosen
    Lee, Maine is a small rural town in Penobscot County known for its forested landscape, outdoor recreation, and close-knit community.
  • B. Lovell, Maine
    Lovell, Maine is a small rural town in Oxford County known for its scenic lakes and mountains in western Maine.
  • C. 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.
  • D. Hope, Maine
    Hope, Maine is a small rural town in coastal Knox County known for its scenic lakes, rolling hills, and quiet New England character.
  • E. Westbrook, Maine
    Westbrook, Maine is a small city in Cumberland County, just west of Portland, known for its historic mill industry and growing residential and commercial development.
  • 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_69d7bdf2b43c819098ae5aa68e61ea58 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96e5a5680819095dcd491486d23e7 completed April 10, 2026, 9:40 p.m.
Created at: April 9, 2026, 5:29 p.m.