Triple
T13775053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brightlingsea |
E330982
|
entity |
| Predicate | hasNatureFeature |
P1094
|
FINISHED |
| Object | salt marshes |
—
|
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: salt marshes | Statement: [Brightlingsea, hasNatureFeature, salt marshes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNatureFeature Context triple: [Brightlingsea, hasNatureFeature, salt marshes]
-
A.
hasNaturalFeature
chosen
Indicates that one entity possesses, contains, or is characterized by a particular natural feature (such as a mountain, river, forest, or coastline).
-
B.
hasNature
Indicates that something possesses, exhibits, or is characterized by a particular inherent quality, essence, or fundamental type.
-
C.
isNaturalFeature
Indicates that the subject is a naturally occurring physical feature of the environment, not created or significantly altered by human activity.
-
D.
hasNaturalAreaType
Indicates that an entity is associated with or classified by a specific type of natural area (e.g., forest, wetland, grassland).
-
E.
hasBiodiversityFeature
Indicates that an entity possesses or is associated with a specific biodiversity-related characteristic, attribute, or element.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0238bdbc8190a946e6e5431632a5 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:10 p.m.