Triple
T2735285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashokan Reservoir |
E60615
|
entity |
| Predicate | allowedActivity |
P273
|
FINISHED |
| Object | shoreline fishing with permit |
—
|
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: shoreline fishing with permit | Statement: [Ashokan Reservoir, allowedActivity, shoreline fishing with permit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowedActivity Context triple: [Ashokan Reservoir, allowedActivity, shoreline fishing with permit]
-
A.
supportsActivity
Indicates that one entity provides the necessary conditions, resources, or environment for another entity’s activity to occur or be sustained.
-
B.
targetedActivity
Indicates that an activity is specifically directed or focused toward a particular entity, group, or objective.
-
C.
allows
chosen
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
D.
protectsActivity
Indicates that one entity safeguards, preserves, or defends the continuation or integrity of another entity’s activity.
-
E.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
- 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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb1022488190af84e536946b2e37 |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd82859348190bce3be8f2e9d60ba |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.