Triple
T20936153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bay Head, New Jersey |
E515588
|
entity |
| Predicate | hasBeachAccessPolicy |
P64364
|
FINISHED |
| Object | beach badges required in season |
—
|
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: beach badges required in season | Statement: [Bay Head, New Jersey, hasBeachAccessPolicy, beach badges required in season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeachAccessPolicy Context triple: [Bay Head, New Jersey, hasBeachAccessPolicy, beach badges required in season]
-
A.
hasBeachTagRequirement
chosen
Indicates that something is subject to a specific requirement or condition related to beach access, use, or tagging.
-
B.
servesBeachAccess
Indicates that something provides or facilitates access to a beach for another entity.
-
C.
hasBeach
Indicates that one entity possesses, includes, or is characterized by a beach as part of its features or environment.
-
D.
hasBeachSection
Indicates that an area, location, or property includes or is associated with a specific section designated as a beach.
-
E.
hasBeachUse
Indicates that an entity is used for, designated for, or associated with beach-related activities or purposes.
- 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_69e0b4fc13408190b06868df03c5c29b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f9527004819082b72bf15e3c6419 |
completed | April 21, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:49 p.m.