Triple
T2691344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Norfolk district |
E58407
|
entity |
| Predicate | hasSeaDefences |
P34503
|
FINISHED |
| Object | North Sea 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: North Sea coast | Statement: [North Norfolk district, hasSeaDefences, North Sea coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeaDefences Context triple: [North Norfolk district, hasSeaDefences, North Sea coast]
-
A.
hasFortifications
Indicates that one entity possesses or is equipped with defensive structures or fortification works associated with it.
-
B.
wasFortifiedBy
Indicates that a place or structure received defensive strengthening or fortification through the actions or resources of a specified agent or entity.
-
C.
hasMoat
Indicates that one entity is surrounded or protected by a moat associated with another entity.
-
D.
hasNavalFacility
Indicates that one entity possesses, hosts, or contains a naval facility (such as a naval base, port, or installation) associated with it.
-
E.
hasBreakwater
chosen
Indicates that a structure or location is equipped with or associated with a breakwater that provides protection from waves or erosion.
- 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_69ab4ac269e481909cb317d79e68b75b |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda0cb9b48190ab354c277cef9e23 |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81c9b4c81908e5e0da6ac5f828b |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.