Triple
T5261935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Island Beach State Park |
E118844
|
entity |
| Predicate | hasAccessRule |
P47431
|
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: [Island Beach State Park, hasAccessRule, day-use only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessRule Context triple: [Island Beach State Park, hasAccessRule, day-use only]
-
A.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
-
B.
hasAccessBy
Indicates that one entity is permitted to access, use, or interact with another entity, typically under specified permissions or conditions.
-
C.
hasRule
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
D.
hasAccessTowards
Indicates that one entity possesses the ability, permission, or means to reach, use, or interact with another entity or resource.
-
E.
hasAccessConstraint
chosen
Indicates that there is a limiting condition or rule governing the ability to access or use a particular resource, service, or action.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bd0c5f48190a1be89314c59f96b |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.