Triple
T8657887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Severn Sound |
E205467
|
entity |
| Predicate | hasEcosystemComponent |
P1888
|
FINISHED |
| Object | coastal wetlands |
—
|
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: coastal wetlands | Statement: [Severn Sound, hasEcosystemComponent, coastal wetlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEcosystemComponent Context triple: [Severn Sound, hasEcosystemComponent, coastal wetlands]
-
A.
containsEcosystem
chosen
Indicates that one entity encompasses or includes an ecosystem within its boundaries or scope.
-
B.
hasEcosystemService
Indicates that one entity provides, supports, or is associated with an ecosystem service that benefits another entity or the environment.
-
C.
supportsEcosystemType
Indicates that one entity provides suitable conditions or resources necessary to sustain or maintain a particular type of ecosystem.
-
D.
operatesInEcosystem
Indicates that an entity functions, behaves, or carries out its activities within a particular ecosystem or environmental context.
-
E.
isCoreComponentOf
Indicates that something is an essential, foundational part required for the structure, function, or identity of 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_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.