Triple
T26275128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henlopen Acres, Delaware |
E660544
|
entity |
| Predicate | nearbyResortCommunity |
P138521
|
FINISHED |
| Object | Rehoboth Beach, Delaware |
—
|
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: Rehoboth Beach, Delaware | Statement: [Henlopen Acres, Delaware, nearbyResortCommunity, Rehoboth Beach, Delaware]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyResortCommunity Context triple: [Henlopen Acres, Delaware, nearbyResortCommunity, Rehoboth Beach, Delaware]
-
A.
nearbyResortArea
Indicates that a resort area is located close to or within a short distance of a specified place or entity.
-
B.
nearbyResortSection
Indicates that one resort section is located close to another resort section in physical proximity.
-
C.
nearbySettlements
chosen
Indicates that one settlement is located close to another settlement in geographic space.
-
D.
hasRecreationalActivityNearby
Indicates that a location has one or more recreational activities or facilities available in its nearby surroundings.
-
E.
nearbyGolfResort
Indicates that one location is situated close enough to another to be considered a conveniently accessible golf resort.
- 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 26, 2026, 9:55 p.m.