Triple
T3195322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arnside |
E66920
|
entity |
| Predicate | hasDesignationNearby |
P46042
|
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: [Arnside, hasDesignationNearby, Site of Special Scientific Interest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDesignationNearby Context triple: [Arnside, hasDesignationNearby, Site of Special Scientific Interest]
-
A.
hasDesignation
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
-
B.
hasCityDesignatedAs
Indicates that an entity has a specific city formally assigned or designated to it in a particular role or capacity.
-
C.
canBeDesignatedBy
Indicates that one entity is capable of being assigned, labeled, or identified by another entity as its designation.
-
D.
hasNearbyFacility
Indicates that one entity is located close to or in the vicinity of a particular facility.
-
E.
hasNearbyBase
Indicates that one entity has a base or facility located in close physical proximity to another entity or location.
- 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_69ad8588ba18819086a10951c32ecb80 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada7163c6c8190b26b05b66740264d |
completed | March 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69ad9e05e4f48190adbe4366cdba2349 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f9259c8190afbc5ad0fa55436b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:07 p.m.