Triple
T1569748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pigeon Lake Wilderness Area |
E33510
|
entity |
| Predicate | hunting |
P30681
|
FINISHED |
| Object | allowed in season under state regulations |
—
|
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: allowed in season under state regulations | Statement: [Pigeon Lake Wilderness Area, hunting, allowed in season under state regulations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hunting Context triple: [Pigeon Lake Wilderness Area, hunting, allowed in season under state regulations]
-
A.
shootsCatches
Indicates that one entity shoots something that is then caught by another entity.
-
B.
predators
Indicates a relationship where one organism hunts, kills, and consumes another organism as a food source.
-
C.
preysOn
Indicates that one entity hunts, kills, and consumes another entity as a food source.
-
D.
hauls
Indicates that one entity pulls, drags, or transports another entity, typically involving effort or force over a distance.
-
E.
fishingActivity
Indicates an activity where an entity engages in catching or attempting to catch fish or other aquatic organisms.
- F. None of above. chosen
Provenance (4 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_69a885f11b048190935025a035302715 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907ba63c88190b60c14dec8d1e40f |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a9607716b4819092187f8c08daaf31 |
completed | March 5, 2026, 10:52 a.m. |
Created at: March 4, 2026, 7:27 p.m.