Triple

T38182746
Position Surface form Disambiguated ID Type / Status
Subject Sunday River E1005216 entity
Predicate hasAssociatedResortTown P19586 FINISHED
Object Newry, 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: Newry, Maine | Statement: [Sunday River, hasAssociatedResortTown, Newry, Maine]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAssociatedResortTown
Context triple: [Sunday River, hasAssociatedResortTown, Newry, Maine]
  • A. isResortTown
    Indicates that a town functions primarily as a resort destination, typically focused on tourism, leisure, and vacation activities.
  • B. associatedResort
    Indicates a relationship where one entity is linked or connected to a specific resort, typically as its related or corresponding resort.
  • C. isResortOf
    Indicates that a location or facility functions as a resort associated with, belonging to, or serving a particular entity (such as a city, region, or organization).
  • D. hasResortCommunity
    Indicates that one entity includes, contains, or is associated with a resort-style residential or vacation community.
  • E. locatedInResortTown chosen
    Indicates that something is situated within the boundaries of a town that is primarily known as a resort or vacation destination.
  • F. None of above.

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_69f76dbc22c481908139b694ffde7a0c completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 completed May 8, 2026, 7:18 a.m.
PD Predicate disambiguation batch_69fd8d8a16f08190b9e880901bfa44fe completed May 8, 2026, 7:15 a.m.
Created at: May 3, 2026, 4:29 p.m.