Triple
T9451113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Fork |
E227893
|
entity |
| Predicate | hasCommunity |
P2605
|
FINISHED |
| Object | Amagansett |
E206743
|
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: Amagansett | Statement: [South Fork, hasCommunity, Amagansett]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amagansett Context triple: [South Fork, hasCommunity, Amagansett]
-
A.
Amagansett
chosen
Amagansett is a small seaside hamlet in the town of East Hampton on Long Island, New York, known for its beaches, historic character, and summer community.
-
B.
Wainscott
Wainscott is a small, affluent hamlet on the South Fork of Long Island, New York, known for its beaches, farmland, and upscale residential character.
-
C.
Wainscott
Wainscott is a village and residential area in Medway, Kent, England, situated near the town of Strood.
-
D.
Cutchogue
Cutchogue is a small hamlet and wine-country community on the North Fork of Long Island in Suffolk County, New York.
-
E.
Montauk
Montauk is a coastal hamlet at the eastern tip of Long Island known for its beaches, fishing, and historic lighthouse.
- 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_69ca8439f8bc8190997f2ef40c9f0bc2 |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f6796d8819088cbecc0588ae5fc |
completed | April 1, 2026, 8:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d139db9d1081908e2014d6f0e7e925 |
completed | April 4, 2026, 4:18 p.m. |
Created at: March 30, 2026, 7:51 p.m.