Triple
T21476847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buchan Ness and Collieston Coast SPA |
E529883
|
entity |
| Predicate | birdInterest |
P29974
|
FINISHED |
| Object | kittiwake |
—
|
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: kittiwake | Statement: [Buchan Ness and Collieston Coast SPA, birdInterest, kittiwake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: birdInterest Context triple: [Buchan Ness and Collieston Coast SPA, birdInterest, kittiwake]
-
A.
birdwatchingFeature
Indicates a feature, characteristic, or amenity that is specifically related to or beneficial for birdwatching activities.
-
B.
birdDiversity
Indicates the variety and richness of different bird species present within a given area, community, or dataset.
-
C.
typicalBird
Indicates that the subject is considered a representative or standard example of a bird, exhibiting the common or characteristic features associated with birds.
-
D.
birdRepresents
Indicates that one bird stands for, symbolizes, or serves as a representation of another entity in some context.
-
E.
hasBirdSpecies
chosen
Indicates that there exists a relationship in which a subject possesses, contains, or is associated with a particular bird species.
- 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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea187a3c8190b3f33bd760dc1f54 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:20 p.m.