Triple
T21254066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sag Harbor Cove |
E523818
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | North Haven |
—
|
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: North Haven | Statement: [Sag Harbor Cove, near, North Haven]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: North Haven Context triple: [Sag Harbor Cove, near, North Haven]
-
A.
North Haven
North Haven is a coastal town in New South Wales, Australia, known for its beaches and relaxed seaside lifestyle.
-
B.
North Haven
North Haven is a small settlement on Holy Isle in the Firth of Clyde, Scotland, known for its tranquil setting and association with spiritual retreat activities.
-
C.
North Haven
North Haven is a coastal suburb in Adelaide, South Australia, known for its marina, beaches, and residential communities.
-
D.
North Haven
North Haven is a small island town off the coast of Maine, known for its scenic beauty, fishing heritage, and popularity as a summer destination.
-
E.
North Haven, New York
chosen
North Haven, New York is a small, affluent residential village on Long Island’s South Fork, known for its waterfront properties and proximity to the Hamptons.
- 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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735a0391881908e45909e939415a5 |
completed | April 21, 2026, 8:30 a.m. |
Created at: April 16, 2026, 3:57 p.m.