Triple
T8657890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Severn Sound |
E205467
|
entity |
| Predicate | hasIssueHistory |
P37550
|
FINISHED |
| Object | nutrient enrichment |
—
|
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: nutrient enrichment | Statement: [Severn Sound, hasIssueHistory, nutrient enrichment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIssueHistory Context triple: [Severn Sound, hasIssueHistory, nutrient enrichment]
-
A.
hasHistoryNote
Indicates that there is an associated historical note or record describing past events, changes, or context related to the subject.
-
B.
hasTypeHistory
Indicates that an entity is associated with a record or sequence of its past and present types or classifications over time.
-
C.
hasHistoryOf
chosen
Indicates that an entity has a documented prior occurrence or background of a specified condition, event, or state.
-
D.
hasFlagHistory
Indicates that there exists a historical record or sequence of changes related to an entity’s flag.
-
E.
hasHistorySince
Indicates that an entity has maintained a particular state, condition, or relationship continuously starting from a specified point in time.
- 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_69ca8350897c819086cde7596fbe5fe7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc486d576081908ad28749c7971432 |
completed | March 31, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:30 p.m.