Triple
T7866921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nissequogue River State Park |
E182638
|
entity |
| Predicate | openingHoursPolicy |
P17011
|
FINISHED |
| Object | day‑use only |
—
|
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: day‑use only | Statement: [Nissequogue River State Park, openingHoursPolicy, day‑use only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingHoursPolicy Context triple: [Nissequogue River State Park, openingHoursPolicy, day‑use only]
-
A.
openingHoursCharacteristic
chosen
Indicates a relationship that specifies particular attributes or features of an entity’s opening hours, such as patterns, exceptions, or special conditions.
-
B.
openingTime
Indicates the time at which a place, service, or event begins operating or becomes accessible.
-
C.
hoursOfOperation
Indicates the time periods during which a place or service is open and available for use.
-
D.
has24HourOperations
Indicates that an entity operates continuously for 24 hours a day without closing.
-
E.
openPitClosedIn
Indicates that an open-pit mine or excavation has been closed, decommissioned, or otherwise taken out of active use at a specified time or under specified conditions.
- 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_69ca82894d9081908a832bfce71a4714 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb38464274819080f182b53783fa84 |
completed | March 31, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69cae925ca388190ae4a01fa76e957e8 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:54 p.m.