Triple
T30361135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London King’s Cross–Hull |
E772288
|
entity |
| Predicate | coastServed |
P99779
|
FINISHED |
| Object | east coast of England |
—
|
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: east coast of England | Statement: [London King’s Cross–Hull, coastServed, east coast of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastServed Context triple: [London King’s Cross–Hull, coastServed, east coast of England]
-
A.
servesCoast
chosen
Indicates that one entity provides transportation, protection, or other services along or for the benefit of a particular coastline.
-
B.
servesCoastalCity
Indicates that one entity provides transportation, services, or support to a city located on or near a coast.
-
C.
islandServed
Indicates that a particular island is provided with service or coverage (such as transportation, utilities, or infrastructure) by a specified entity.
-
D.
includesCoastOf
Indicates that one geographic or administrative entity encompasses or contains the coastline of another entity.
-
E.
connectsToCoastAt
Indicates that one entity has a direct physical or geographical connection or access to a coastline at the location of another entity.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68242fc208190ae8a9ab1a4bdccfd |
completed | May 2, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:58 p.m.