Triple
T19192521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revillagigedo Islands |
E469876
|
entity |
| Predicate | fishingStatus |
P134811
|
FINISHED |
| Object | no-take marine reserve |
—
|
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: no-take marine reserve | Statement: [Revillagigedo Islands, fishingStatus, no-take marine reserve]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fishingStatus Context triple: [Revillagigedo Islands, fishingStatus, no-take marine reserve]
-
A.
fishingActivity
Indicates an activity where an entity engages in catching or attempting to catch fish or other aquatic organisms.
-
B.
gameFishStatus
Indicates the classification of an entity in terms of its status as a game fish, such as whether it is considered a target species for recreational or sport fishing.
-
C.
fishingType
Indicates the specific method or style of fishing associated with an activity, event, or location.
-
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. chosen
Provenance (4 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f8a3434881908acc4063a9ee9386 |
completed | April 20, 2026, 9:57 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:07 p.m.