Triple
T27223244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Toms River, New Jersey |
E681336
|
entity |
| Predicate | isInCoastalCounty |
P156876
|
FINISHED |
| Object | Ocean County, New Jersey |
—
|
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: Ocean County, New Jersey | Statement: [South Toms River, New Jersey, isInCoastalCounty, Ocean County, New Jersey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInCoastalCounty Context triple: [South Toms River, New Jersey, isInCoastalCounty, Ocean County, New Jersey]
-
A.
isCoastalCounty
Indicates that a county is located along a coastline, bordering an ocean or sea.
-
B.
isInCoastalRegion
chosen
Indicates that a location or area is situated within a coastal region, typically near or along a sea or ocean shoreline.
-
C.
isInCoastalTown
Indicates that one entity (typically a place or object) is located within a town that is situated along a coast.
-
D.
isCoastalCountyLevelCityOf
Indicates that one entity is a county-level city that is located on or directly adjacent to a coastline within the jurisdiction of another entity.
-
E.
isCoastalDistrict
Indicates that a district is located along a coastline or has direct access to a sea or ocean.
- 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_69eefac9f64c8190a07490fe0c8b72a3 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6264866248190af21260780020fac |
completed | May 2, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 9:43 a.m.