Triple
T24738982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trio people |
E618494
|
entity |
| Predicate | traditionalFishingMethods |
P54152
|
FINISHED |
| Object | fish poison |
—
|
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: fish poison | Statement: [Trio people, traditionalFishingMethods, fish poison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalFishingMethods Context triple: [Trio people, traditionalFishingMethods, fish poison]
-
A.
traditionalFishingMethod
chosen
Indicates a relationship where a fishing activity is carried out using long-established, customary techniques passed down through local or ancestral practice.
-
B.
fishingType
Indicates the specific method or style of fishing associated with an activity, event, or location.
-
C.
historicallyFishedBy
Indicates that an area or body of water has been used for fishing by a particular entity or group in the past.
-
D.
fishingUse
Indicates that one entity uses another as a tool, method, or context specifically for the activity of fishing.
-
E.
fishingActivity
Indicates an activity where an entity engages in catching or attempting to catch fish or other aquatic organisms.
- 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_69e2fab8f95c81908bb9e552cf3280c2 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 4:04 a.m.