Triple
T747244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Branch Reservoir |
E15369
|
entity |
| Predicate | hasFishingRegulations |
P18323
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Middle Branch Reservoir, hasFishingRegulations, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFishingRegulations Context triple: [Middle Branch Reservoir, hasFishingRegulations, yes]
-
A.
recreationRegulation
chosen
Indicates rules, restrictions, or guidelines governing recreational activities or leisure use of a place or resource.
-
B.
stateFish
Indicates that an entity is a fish that serves as the official state fish of a particular political region.
-
C.
hasMarineResource
Indicates that one entity possesses, contains, or is associated with a marine (ocean or sea-based) resource in relation to another entity.
-
D.
permitsTestingTheWaters
Indicates that one party allows another to explore or try something on a limited or provisional basis before making a full commitment.
-
E.
hasNearbyLake
Indicates that one entity is located close to or in the vicinity of a lake.
- 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a62dd1bc819094a3814654448ae3 |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a4ff10608190bfd60b4a1cb38f7d |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.