Triple
T16352439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandgate |
E397091
|
entity |
| Predicate | hasNearbyPlace |
P3449
|
FINISHED |
| Object | Seabrook |
E1045791
|
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: Seabrook | Statement: [Sandgate, hasNearbyPlace, Seabrook]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Seabrook Context triple: [Sandgate, hasNearbyPlace, Seabrook]
-
A.
Seabrook
Seabrook is a residential area or neighborhood located within the town of Mashpee on Cape Cod in Massachusetts.
-
B.
Seabrook
Seabrook is a residential suburb in Melbourne’s western region, located within the City of Hobsons Bay in Victoria, Australia.
-
C.
Seabrook
chosen
Seabrook is a coastal village in Kent, England, situated between Sandgate and Hythe on the English Channel.
-
D.
Seabrook station
Seabrook station is a commuter rail stop in Seabrook, Maryland, served by MARC trains on the Penn Line between Washington, D.C., and Baltimore.
-
E.
Seabrook, New Hampshire
Seabrook, New Hampshire is a coastal town in southeastern New Hampshire known for its beaches and the Seabrook Station nuclear power plant.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2facbf60c8190aa47d4c45ff59354 |
completed | April 18, 2026, 3:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a002db6375c81908c64dbe2bc987b1a |
completed | May 10, 2026, 7:03 a.m. |
Created at: April 10, 2026, 5:07 a.m.