Triple

T10569831
Position Surface form Disambiguated ID Type / Status
Subject Portland metropolitan area E249448 entity
Predicate containsTown P847 FINISHED
Object Scarborough, Maine E368770 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: Scarborough, Maine | Statement: [Portland metropolitan area, containsTown, Scarborough, Maine]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Scarborough, Maine
Context triple: [Portland metropolitan area, containsTown, Scarborough, Maine]
  • A. Scarborough, Maine chosen
    Scarborough, Maine is a coastal town in southern Maine known for its beaches, marshlands, and proximity to the city of Portland.
  • B. Waterford, Maine
    Waterford, Maine is a small rural town in Oxford County known for its lakes, forests, and traditional New England village character.
  • C. Searsmont, Maine
    Searsmont, Maine is a small rural town in Waldo County known for its forests, lakes, and traditional New England character.
  • D. Ripley, Maine
    Ripley, Maine is a small rural town located in Somerset County in central Maine.
  • E. Sanford, Maine
    Sanford, Maine is a city in York County known for its historic textile mill heritage and its location in southern Maine near the New Hampshire border.
  • 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_69d381c8bd708190acf3d275c908251e completed April 6, 2026, 9:50 a.m.
NER Named-entity recognition batch_69d52730fd4481908b3f4eb80ca209f2 completed April 7, 2026, 3:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69ff5f1f80648190a4a0e8260ac95194 completed May 9, 2026, 4:21 p.m.
Created at: April 6, 2026, 12:37 p.m.