Triple
T24740597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuckahoe, New Jersey |
E618546
|
entity |
| Predicate | nearShoreDestination |
P157073
|
FINISHED |
| Object | Ocean City, 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 City, New Jersey | Statement: [Tuckahoe, New Jersey, nearShoreDestination, Ocean City, New Jersey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearShoreDestination Context triple: [Tuckahoe, New Jersey, nearShoreDestination, Ocean City, New Jersey]
-
A.
nearestSea
Indicates that one location is the closest sea to a given place compared to all other seas.
-
B.
nearbyStrait
Indicates that one entity is located close to or adjacent to a particular strait.
-
C.
stateOnNearestShore
Indicates that an entity is located on the shore that is geographically closest to another specified reference point or entity.
-
D.
hasNearbyHarbor
Indicates that one location has a harbor situated close to it in geographic proximity.
-
E.
nearbyIslandDestination
Indicates that one location serves as an island destination situated a short distance away from another reference point or place.
- F. None of above. chosen
Provenance (4 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_69e2fab8f95c81908bb9e552cf3280c2 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a25ab88190a72db43043c1f6ff |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f410a001788190a457e41f53aaf90c |
completed | May 1, 2026, 2:32 a.m. |
Created at: April 18, 2026, 4:05 a.m.