Triple
T32717950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Uist and Berneray |
E836573
|
entity |
| Predicate | hasProtectedHabitat |
P203005
|
FINISHED |
| Object | machair |
—
|
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: machair | Statement: [North Uist and Berneray, hasProtectedHabitat, machair]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtectedHabitat Context triple: [North Uist and Berneray, hasProtectedHabitat, machair]
-
A.
hasProtectedSpecies
Indicates that the subject contains, supports, or is associated with one or more species that are legally or formally designated as protected.
-
B.
hasProtectedAreasNearby
Indicates that an entity is located close to one or more designated protected or conservation areas.
-
C.
situatedInProtectedArea
Indicates that an entity is located within the boundaries of a designated protected area (such as a reserve, park, or conservation zone).
-
D.
locatedInProtectedEcoregion
Indicates that an entity is situated within a designated protected ecological region or conservation area.
-
E.
hasConservationCorridor
Indicates that there exists a designated ecological or wildlife corridor connecting two areas to support species movement and habitat continuity.
- F. None of above. chosen
Provenance (4 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_69f34935455881909088975d79460418 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a00d9717a9881908194163d719f14d6 |
completed | May 10, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a00d91db2ec81909ebacfc9f0d11dd8 |
completed | May 10, 2026, 7:14 p.m. |
| PDg | Predicate description generation | batch_6a00d970a11081908f24876a0696d827 |
completed | May 10, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:11 a.m.