Triple
T30967384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Rhyl Offshore Wind Farm (planned) |
E788994
|
entity |
| Predicate | coastlineReference |
P130358
|
FINISHED |
| Object | north coast of Wales |
—
|
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 coast of Wales | Statement: [North Rhyl Offshore Wind Farm (planned), coastlineReference, north coast of Wales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastlineReference Context triple: [North Rhyl Offshore Wind Farm (planned), coastlineReference, north coast of Wales]
-
A.
coastlineFeature
Indicates that a geographic entity is a specific type of feature located along or forming part of a coastline.
-
B.
coastlineAssociation
chosen
Indicates an association between an entity and a coastline, such as adjacency, alignment, or functional connection to that coastal boundary.
-
C.
countryCoastlineOf
Indicates that a country has the specified coastline as part of its national territory or boundary.
-
D.
coastName
Indicates that an entity is identified by the name of a specific coast or coastal region.
-
E.
hasCoastlineName
Indicates that a geographic entity’s coastline is known by a particular name.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:54 p.m.