Triple
T7740775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wildwood, New Jersey |
E175501
|
entity |
| Predicate | hasBeachTagPolicy |
P64364
|
FINISHED |
| Object | no beach tags required |
—
|
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: no beach tags required | Statement: [Wildwood, New Jersey, hasBeachTagPolicy, no beach tags required]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeachTagPolicy Context triple: [Wildwood, New Jersey, hasBeachTagPolicy, no beach tags required]
-
A.
hasBeachTagRequirement
chosen
Indicates that something is subject to a specific requirement or condition related to beach access, use, or tagging.
-
B.
hasBeachSection
Indicates that an area, location, or property includes or is associated with a specific section designated as a beach.
-
C.
hasBeach
Indicates that one entity possesses, includes, or is characterized by a beach as part of its features or environment.
-
D.
hasBeachUse
Indicates that an entity is used for, designated for, or associated with beach-related activities or purposes.
-
E.
beachSectorSupported
Indicates that a particular beach sector is maintained, serviced, or otherwise operationally supported by a responsible party or system.
- 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_69c6995f9c60819092e386192bd63c6f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c7016c4a748190a7012030edaefcee |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:07 p.m.