Triple
T18198304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Lawrence–FDR Power Project |
E435716
|
entity |
| Predicate | hasFishProtectionMeasures |
P130189
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [St. Lawrence–FDR Power Project, hasFishProtectionMeasures, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFishProtectionMeasures Context triple: [St. Lawrence–FDR Power Project, hasFishProtectionMeasures, true]
-
A.
hasProtectedSpecies
Indicates that the subject contains, supports, or is associated with one or more species that are legally or formally designated as protected.
-
B.
hasFishingSpecies
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
-
C.
fishingPolicy
Indicates the rules, regulations, or management approach governing fishing activities and resource use.
-
D.
hasFishCountingFacility
Indicates that a location or structure is equipped with a facility specifically designed for counting fish.
-
E.
containsFishery
Indicates that one entity includes, encompasses, or has within its area a fishery or fishing-related operation.
- 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e0d47f1c819082eec59492497797 |
completed | April 19, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f684e48190b38c64b58c518b6a |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:31 a.m.