Triple
T6760841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crab Replenishment Reserve |
E154585
|
entity |
| Predicate | hasPrimaryBenefit |
P25020
|
FINISHED |
| Object | support of local fisheries |
—
|
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: support of local fisheries | Statement: [Crab Replenishment Reserve, hasPrimaryBenefit, support of local fisheries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryBenefit Context triple: [Crab Replenishment Reserve, hasPrimaryBenefit, support of local fisheries]
-
A.
hasBenefit
Indicates that one entity provides an advantage, improvement, or positive outcome to another entity.
-
B.
primaryBenefit
chosen
Indicates that one entity serves as the main or most important advantage, gain, or positive outcome associated with another entity.
-
C.
isIndividualBenefit
Indicates that something provides a benefit or advantage to a single individual rather than to a group or collective.
-
D.
benefitsAre
Indicates that certain advantages, gains, or positive outcomes are possessed by or accrue to a particular entity or group.
-
E.
affectsBenefit
Indicates that one entity has an influence on, modifies, or determines the benefit or advantage received by another entity.
- 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_69c688109c1c8190added9a221292af0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d327e37081909d576e6eff9eec97 |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d09227108190b253b91967831a85 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:12 p.m.