Triple
T37561996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meliden |
E933845
|
entity |
| Predicate | hasProximityToCoast |
P17623
|
FINISHED |
| Object | near Irish Sea coast via Prestatyn |
—
|
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: near Irish Sea coast via Prestatyn | Statement: [Meliden, hasProximityToCoast, near Irish Sea coast via Prestatyn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProximityToCoast Context triple: [Meliden, hasProximityToCoast, near Irish Sea coast via Prestatyn]
-
A.
hasNearbyCoast
chosen
Indicates that one location is situated close to a coastline or seashore.
-
B.
hasMaximumDistanceFromCoast
Indicates that an entity is located at the greatest possible distance from any coastline within a specified area or context.
-
C.
distanceFromCoast
Indicates the measured spatial separation between a location and the nearest point on a coastline.
-
D.
isCoastalTo
Indicates that one place is located along or directly borders the coastline of another body of water or coastal region.
-
E.
hasShoreNear
Indicates that one entity is located close enough to another entity’s shore or coastline to be considered nearby.
- 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_69f76ecb4acc8190b53f96d0b013e415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.