Triple
T10509369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wormley |
E247870
|
entity |
| Predicate | nearbyProtectedAreaStatus |
P67111
|
FINISHED |
| Object | Site 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: Site of Special Scientific Interest | Statement: [Wormley, nearbyProtectedAreaStatus, Site of Special Scientific Interest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyProtectedAreaStatus Context triple: [Wormley, nearbyProtectedAreaStatus, Site of Special Scientific Interest]
-
A.
nearbyProtectedSite
chosen
Indicates that one entity is located close to a protected site, such as a reserve, park, or conservation area.
-
B.
hasNearbyNatureReserve
Indicates that one place or entity is located close to a designated nature reserve.
-
C.
nearestMajorProtectedArea
Indicates the closest significant legally protected natural area to a given location or entity.
-
D.
hasNearbyWildernessArea
Indicates that a wilderness area is located within a close geographic proximity to the referenced place or entity.
-
E.
hasNeighbouringProtectedArea
Indicates that one protected area is directly adjacent to or shares a boundary with another protected area.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509b359ac8190b3683cc6b9c70a71 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb919ea08190bcc1193e2014d437 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:27 p.m.