Triple
T9081586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilhas Selvagens |
E217638
|
entity |
| Predicate | fishingRegulation |
P51236
|
FINISHED |
| Object | fishing heavily restricted |
—
|
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: fishing heavily restricted | Statement: [Ilhas Selvagens, fishingRegulation, fishing heavily restricted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fishingRegulation Context triple: [Ilhas Selvagens, fishingRegulation, fishing heavily restricted]
-
A.
fishingPolicy
chosen
Indicates the rules, regulations, or management approach governing fishing activities and resource use.
-
B.
fishingActivity
Indicates an activity where an entity engages in catching or attempting to catch fish or other aquatic organisms.
-
C.
fishingType
Indicates the specific method or style of fishing associated with an activity, event, or location.
-
D.
commercialFishingAllowed
Indicates that engaging in commercial fishing activities is permitted in the specified area or context.
-
E.
fisheryType
Indicates the specific category or kind of fishery associated with an entity, such as its operational or regulatory classification.
- 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_69ca83d7a0388190ba1af89ed7ba36f9 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc9608a82481908918821884ba5796 |
completed | April 1, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69cc65fa79bc81908b46f05c8bba920f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:13 p.m.