Triple
T16727711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pembroke |
E406503
|
entity |
| Predicate | hasNearbyTown |
P3883
|
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, hasNearbyTown, Pembroke Dock]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pembroke Dock Context triple: [Pembroke, hasNearbyTown, 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.
Dungeness Dock
Dungeness Dock is a waterfront landing area associated with the historic Dungeness estate on Cumberland Island, Georgia, serving as a primary access point by boat.
-
C.
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.
-
D.
Salisbury Dock
Salisbury Dock is a historic maritime dock in Liverpool, England, forming part of the city’s northern dock system along the River Mersey.
-
E.
Stalbridge Dock
Stalbridge Dock is a component basin within the Garston Docks complex in Liverpool, historically used for handling maritime cargo and shipping.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e38748f538819097de1fdee9b42f34 |
completed | April 18, 2026, 1:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a009d483a8c8190b127f32dcc21be5a |
completed | May 10, 2026, 2:59 p.m. |
Created at: April 10, 2026, 5:20 a.m.