Triple
T11523839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Thurne |
E273235
|
entity |
| Predicate | hasEcologicalDesignationNearby |
P96189
|
FINISHED |
| Object | Sites of Special Scientific Interest |
—
|
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: Sites of Special Scientific Interest | Statement: [River Thurne, hasEcologicalDesignationNearby, Sites of Special Scientific Interest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEcologicalDesignationNearby Context triple: [River Thurne, hasEcologicalDesignationNearby, Sites of Special Scientific Interest]
-
A.
hasNearbyNatureReserve
Indicates that one place or entity is located close to a designated nature reserve.
-
B.
hasProtectedAreasNearby
chosen
Indicates that an entity is located close to one or more designated protected or conservation areas.
-
C.
hasNearbyHabitats
Indicates that one entity has other habitats located close to it in geographic or spatial terms.
-
D.
hasNearbyWildernessArea
Indicates that a wilderness area is located within a close geographic proximity to the referenced place or entity.
-
E.
hasNearbyWetlandRegion
Indicates that a given location or area is situated close to, or in the vicinity of, a wetland region.
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d87fd26648819083de19bcddf8ad69 |
completed | April 10, 2026, 4:42 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.