Triple
T30285436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BCP Council |
E770220
|
entity |
| Predicate | hasCoastalJurisdiction |
P81007
|
FINISHED |
| Object | English Channel coast |
—
|
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: English Channel coast | Statement: [BCP Council, hasCoastalJurisdiction, English Channel coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalJurisdiction Context triple: [BCP Council, hasCoastalJurisdiction, English Channel coast]
-
A.
isCoastalJurisdiction
chosen
Indicates that a jurisdiction has a coastline or direct access to a sea or ocean, giving it coastal status.
-
B.
hasCoastalDistrict
Indicates that an administrative region or area includes at least one district that borders a sea or ocean.
-
C.
hasCoastalRegion
Indicates that a place possesses at least one region that borders or is directly adjacent to a sea or ocean.
-
D.
hasCoastalEnclave
Indicates that one territory possesses a non-contiguous portion of its land that is coastal and entirely surrounded by another territory.
-
E.
hasCoastlineDesignation
Indicates that a geographic area’s coastline has been assigned a specific official classification or status.
- 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a012594c27081908c80f0e0e6010290 |
completed | May 11, 2026, 12:40 a.m. |
| PD | Predicate disambiguation | batch_6a01252350548190b1df9edc9e581e91 |
completed | May 11, 2026, 12:38 a.m. |
Created at: April 29, 2026, 7:46 p.m.