Triple
T4006688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pembroke |
E89541
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Tenby |
E121850
|
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: Tenby | Statement: [Pembroke, near, Tenby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tenby Context triple: [Pembroke, near, Tenby]
-
A.
Tenby
chosen
Tenby is a historic seaside town and popular tourist resort in Pembrokeshire, Wales, known for its sandy beaches, medieval town walls, and picturesque harbor.
-
B.
Newlyn
Newlyn is a historic Cornish fishing village and harbour on the coast of southwest England, renowned for its art colony and maritime heritage.
-
C.
Haverfordwest
Haverfordwest is a historic market town in southwest Wales that serves as the principal commercial and administrative centre of Pembrokeshire.
-
D.
Narberth
Narberth is a small market town in southwest Wales known for its independent shops, arts scene, and historic castle remains.
-
E.
Penryn
Penryn is a historic town and former parliamentary borough in Cornwall, 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_69b54c67eddc819097eff878c860f3d5 |
completed | March 14, 2026, 11:54 a.m. |
Created at: March 9, 2026, 3:34 p.m.