Triple
T26522860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Perth Amboy |
E670002
|
entity |
| Predicate | isWaterfrontCommunityOn |
P119809
|
FINISHED |
| Object | Raritan Bay |
—
|
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: Raritan Bay | Statement: [City of Perth Amboy, isWaterfrontCommunityOn, Raritan Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWaterfrontCommunityOn Context triple: [City of Perth Amboy, isWaterfrontCommunityOn, Raritan Bay]
-
A.
isWaterfrontSuburb
Indicates that a suburb is located directly adjacent to a body of water, such as a sea, lake, or river.
-
B.
isWaterfrontDistrict
Indicates that a district is located directly along a body of water, such as a river, lake, or coastline.
-
C.
isWaterfrontBuilding
Indicates that a building is located directly adjacent to a body of water, such as a river, lake, or ocean.
-
D.
hasWaterfrontType
Indicates that an entity is associated with a specific type or category of waterfront (e.g., oceanfront, lakefront, riverfront).
-
E.
isWaterfrontSettlement
chosen
Indicates that a settlement is located directly adjacent to a body of water, such as a sea, lake, or river.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613c35b5481909ef85d87d1604be9 |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:29 a.m.