Triple
T3329574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wallasey |
E70000
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Seacombe |
E264863
|
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: Seacombe | Statement: [Wallasey, contains, Seacombe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Seacombe Context triple: [Wallasey, contains, Seacombe]
-
A.
Seacombe
chosen
Seacombe is a riverside district and ferry terminal on the Wirral Peninsula in England, serving as a key Mersey crossing point to Liverpool.
-
B.
Combe
Combe is a small rural village in Oxfordshire, England, known for its traditional English countryside character and proximity to the River Evenlode.
-
C.
Cambourne
Cambourne is a modern, rapidly growing new town in Cambridgeshire, England, developed in the late 20th century and known for its planned residential communities and local amenities.
-
D.
Farncombe
Farncombe is a village in Surrey, England, situated just north of the town of Godalming.
-
E.
Newbourne
Newbourne is a small rural village and civil parish in the English county of Suffolk, known for its countryside setting and traditional village character.
- 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_69ad85a24f208190bcf83131bfed3521 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb171ee0881908642504ab0ac8329 |
completed | March 8, 2026, 5:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b31a810e2c8190bfc206bdeb1ac5b8 |
completed | March 12, 2026, 7:56 p.m. |
Created at: March 8, 2026, 3:12 p.m.