Triple
T31331795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Essex River |
E799049
|
entity |
| Predicate | hasRecreationalAccessType |
P106790
|
FINISHED |
| Object | public boat ramps |
—
|
LITERAL 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: public boat ramps | Statement: [Essex River, hasRecreationalAccessType, public boat ramps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecreationalAccessType Context triple: [Essex River, hasRecreationalAccessType, public boat ramps]
-
A.
hasRecreationalUseRestriction
Indicates that there is a limitation or prohibition on how an entity may be used for recreational purposes.
-
B.
isRecreationalGateway
chosen
Indicates that something serves as an entry point or access hub for recreational activities or leisure experiences.
-
C.
isRecreationalResourceFor
Indicates that something serves as a facility, area, or service used by someone for leisure, recreation, or enjoyment.
-
D.
isRecreationalArea
Indicates that a place or space is designated and used primarily for leisure, relaxation, or recreational activities.
-
E.
hasRecreationalAspect
Indicates that something includes, involves, or is characterized by a recreational or leisure-related component or purpose.
- 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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a013f09b0988190ba3179c7d56c726a |
completed | May 11, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_6a013e600e248190a1a9c363702c8586 |
completed | May 11, 2026, 2:26 a.m. |
Created at: April 29, 2026, 9:16 p.m.