Triple
T27142527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moy catchment |
E681851
|
entity |
| Predicate | hasFisheryManagementUnit |
P56070
|
FINISHED |
| Object | Moy Fishery |
—
|
NE NERFINISHED |
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: Moy Fishery | Statement: [Moy catchment, hasFisheryManagementUnit, Moy Fishery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFisheryManagementUnit Context triple: [Moy catchment, hasFisheryManagementUnit, Moy Fishery]
-
A.
partOfFisheryManagementArea
Indicates that one entity is located within or belongs to a designated fishery management area used for regulating fishing activities.
-
B.
managedForFisheriesBy
Indicates that the management or oversight of fisheries-related activities or resources is carried out by a specified agent or authority.
-
C.
containsFishery
chosen
Indicates that one entity includes, encompasses, or has within its area a fishery or fishing-related operation.
-
D.
hasMarineManagement
Indicates that an entity exercises authority or responsibility over the planning, regulation, or stewardship of marine areas or resources.
-
E.
hasFishProtectionMeasures
Indicates that there are specific measures or practices in place to protect fish populations or their habitats.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 27, 2026, 9:10 a.m.