Triple
T4197171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Branch Reservoir |
E89180
|
entity |
| Predicate | hasRestrictedActivity |
P47431
|
FINISHED |
| Object | swimming |
—
|
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: swimming | Statement: [West Branch Reservoir, hasRestrictedActivity, swimming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRestrictedActivity Context triple: [West Branch Reservoir, hasRestrictedActivity, swimming]
-
A.
mayRestrictActivity
Indicates that one entity has the authority or ability to limit, constrain, or prohibit certain actions or behaviors of another entity.
-
B.
hasDisabledAccess
Indicates that an entity provides facilities, features, or accommodations that make it accessible to people with disabilities.
-
C.
hasAccessRestrictionHistory
Indicates that there exists a record or sequence of past changes detailing how access to something has been restricted over time.
-
D.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
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_69aed9569a4481908b6c1fcec2a11e21 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af035f9f788190a4bcfeda646fbebf |
completed | March 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69af01959c4881909eb1adcb3bdadbe6 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:46 p.m.