Triple
T17308834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Absecon Creek |
E420236
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Absecon Bay |
E548459
|
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: Absecon Bay | Statement: [Absecon Creek, near, Absecon Bay]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Absecon Bay Context triple: [Absecon Creek, near, Absecon Bay]
-
A.
Absecon Bay
chosen
Absecon Bay is a tidal bay along the New Jersey coast near Atlantic City, known for its marshlands, boating, and coastal wildlife habitat.
-
B.
Absecon Inlet
Absecon Inlet is a tidal body of water along the Atlantic coast of New Jersey that separates Atlantic City from the mainland and connects to the Atlantic Ocean.
-
C.
Barnegat Inlet
Barnegat Inlet is a tidal waterway on the New Jersey coast that connects Barnegat Bay with the Atlantic Ocean and is known for its challenging navigation and historic lighthouse.
-
D.
Barnegat Bay
Barnegat Bay is a shallow, lagoon-type estuary along the New Jersey coast known for its coastal ecosystems, recreational boating, and fishing.
-
E.
Absecon
Absecon is a small city in Atlantic County, New Jersey, located near Atlantic City and served by regional rail and highway connections.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43900eca88190930af0e4ec4fc0f9 |
completed | April 19, 2026, 2:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0180e30934819087b7c838c8874aff |
completed | May 11, 2026, 7:10 a.m. |
Created at: April 10, 2026, 5:43 a.m.