Triple
T4006687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pembroke |
E89541
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Pembroke Dock |
E134035
|
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: Pembroke Dock | Statement: [Pembroke, near, Pembroke Dock]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pembroke Dock Context triple: [Pembroke, near, Pembroke Dock]
-
A.
Pembroke Dock
chosen
Pembroke Dock is a coastal town in southwest Wales known historically for its naval dockyard and shipbuilding heritage.
-
B.
Glasson Dock
Glasson Dock is a small port village in Lancashire, England, known for its historic dock and marina at the mouth of the River Lune.
-
C.
Huskisson Dock
Huskisson Dock is a historic dock within the Port of Liverpool in England, known for its role in the city’s maritime trade and industrial heritage.
-
D.
Colman Dock
Colman Dock is a major ferry terminal on Seattle’s downtown waterfront that serves as a key hub for Washington State Ferries across Puget Sound.
-
E.
Brocklebank Dock
Brocklebank Dock is one of the docks within the Port of Liverpool, historically used for commercial shipping and maritime trade on the River Mersey in England.
- 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_69aed9585e788190bec2d39deba3750f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa62d0e081909aaed2978a840734 |
completed | March 9, 2026, 4:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5629004208190964cb4d2e75b0a05 |
completed | March 14, 2026, 1:28 p.m. |
Created at: March 9, 2026, 3:34 p.m.