Triple
T14765015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neyland |
E346969
|
entity |
| Predicate | waterBody |
P1778
|
FINISHED |
| Object | Milford Haven |
E69564
|
NE 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: Milford Haven | Statement: [Neyland, waterBody, Milford Haven]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Milford Haven Context triple: [Neyland, waterBody, Milford Haven]
-
A.
Milford Haven
chosen
Milford Haven is a coastal town and deep-water port in Pembrokeshire, Wales, known for its large natural harbour and role in the UK energy industry.
-
B.
Crosshaven
Crosshaven is a coastal village in County Cork, Ireland, known for its large marina, sailing traditions, and scenic position at the mouth of Cork Harbour.
-
C.
Newlyn
Newlyn is a historic Cornish fishing village and harbour on the coast of southwest England, renowned for its art colony and maritime heritage.
-
D.
Penryn Harbour
Penryn Harbour is a small tidal port and waterfront area serving the historic town of Penryn in Cornwall, England.
-
E.
Amlwch Harbour
Amlwch Harbour is a historic coastal port on the north coast of Anglesey in Wales, once central to the region’s copper mining and maritime trade.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7f576c881909da70627f5897c94 |
completed | April 14, 2026, 11:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe6b4531fc819084d9ab1c86cb540c |
completed | May 8, 2026, 11:01 p.m. |
Created at: April 10, 2026, 1:30 a.m.