Triple
T37901112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European seabass |
E945412
|
entity |
| Predicate | recreationalFishing |
P126008
|
FINISHED |
| Object | popular angling target |
—
|
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: popular angling target | Statement: [European seabass, recreationalFishing, popular angling target]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recreationalFishing Context triple: [European seabass, recreationalFishing, popular angling target]
-
A.
fishingActivity
Indicates an activity where an entity engages in catching or attempting to catch fish or other aquatic organisms.
-
B.
fishingUse
Indicates that one entity uses another as a tool, method, or context specifically for the activity of fishing.
-
C.
fishingType
Indicates the specific method or style of fishing associated with an activity, event, or location.
-
D.
fishedFor
chosen
Indicates that one entity attempted to catch another entity (typically an animal or resource) by engaging in fishing activities.
-
E.
fishingStatus
Indicates the current state or condition of an entity with respect to engaging in fishing activity (e.g., actively fishing, not fishing, or otherwise classified).
- 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.