Triple
T14168912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argungu Fishing Festival |
E351151
|
entity |
| Predicate | usesFishingMethod |
P81811
|
FINISHED |
| Object | hand fishing |
—
|
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: hand fishing | Statement: [Argungu Fishing Festival, usesFishingMethod, hand fishing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFishingMethod Context triple: [Argungu Fishing Festival, usesFishingMethod, hand fishing]
-
A.
fishingUse
Indicates that one entity uses another as a tool, method, or context specifically for the activity of fishing.
-
B.
fishingType
chosen
Indicates the specific method or style of fishing associated with an activity, event, or location.
-
C.
traditionalFishingMethod
Indicates a relationship where a fishing activity is carried out using long-established, customary techniques passed down through local or ancestral practice.
-
D.
fishingActivity
Indicates an activity where an entity engages in catching or attempting to catch fish or other aquatic organisms.
-
E.
hasFishingSpecies
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b472288190b4a271daa54aa6cd |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1 a.m.