Triple
T17617227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waitahanui River |
E429114
|
entity |
| Predicate | hasFishingMethod |
P81811
|
FINISHED |
| Object | fly fishing from river mouth |
—
|
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: fly fishing from river mouth | Statement: [Waitahanui River, hasFishingMethod, fly fishing from river mouth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFishingMethod Context triple: [Waitahanui River, hasFishingMethod, fly fishing from river mouth]
-
A.
hasFishingSpecies
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
-
B.
fishingType
chosen
Indicates the specific method or style of fishing associated with an activity, event, or location.
-
C.
fishingActivity
Indicates an activity where an entity engages in catching or attempting to catch fish or other aquatic organisms.
-
D.
fishedFor
Indicates that one entity attempted to catch another entity (typically an animal or resource) by engaging in fishing activities.
-
E.
fishingUse
Indicates that one entity uses another as a tool, method, or context specifically for the activity of fishing.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d33a2b081908deecee773c333af |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.