Triple
T19231548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish National Scenic Areas |
E480881
|
entity |
| Predicate | haveProtectionFor |
P15793
|
FINISHED |
| Object | landscape character |
—
|
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: landscape character | Statement: [Scottish National Scenic Areas, haveProtectionFor, landscape character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveProtectionFor Context triple: [Scottish National Scenic Areas, haveProtectionFor, landscape character]
-
A.
isProtectedFor
chosen
Indicates that one entity is safeguarded or preserved specifically for the benefit, use, or rights of another entity.
-
B.
hasProtectionCriterion
Indicates that something is associated with a specific condition or standard used to determine its protection requirements or status.
-
C.
isProtectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
D.
providesProtectionIn
Indicates that one entity offers protection or safeguarding to another entity within a specified context, location, or situation.
-
E.
hasProtectionPurpose
Indicates that something is intended or designed to serve a protective function or goal.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa9db56081908f50d318d7fc9eaa |
completed | April 20, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:25 p.m.