Triple
T22837961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torridge District |
E565996
|
entity |
| Predicate | includesCoastalAreas |
P5879
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Torridge District, includesCoastalAreas, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCoastalAreas Context triple: [Torridge District, includesCoastalAreas, true]
-
A.
includesCoastOf
Indicates that one geographic or administrative entity encompasses or contains the coastline of another entity.
-
B.
isCoastalArea
Indicates that a given area is located along or directly adjacent to a sea or ocean coastline.
-
C.
includesCoastalTown
Indicates that a geographic area or region contains at least one town located on or directly adjacent to a coastline.
-
D.
includesCoastalStates
Indicates that a geographic or political region contains one or more states that have a coastline.
-
E.
containsCoastalFeature
chosen
Indicates that one entity geographically includes or encompasses a coastal feature (such as a beach, cliff, bay, or shoreline) within its area or boundaries.
- 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_69e245869e188190a196584f36e682da |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e8244dc819089c0a7525fb512ab |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:35 p.m.