Triple
T13890678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plym Estuary |
E333960
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Plymstock |
E823584
|
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: Plymstock | Statement: [Plym Estuary, adjacentTo, Plymstock]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Plymstock Context triple: [Plym Estuary, adjacentTo, Plymstock]
-
A.
Plymstock
chosen
Plymstock is a suburban area of Plymouth in Devon, England, known for its residential neighborhoods and proximity to the city centre and waterfront.
-
B.
Plympton
Plympton is a historic town in Devon, England, known for its medieval significance and role in the region’s tin-mining administration.
-
C.
Popley
Popley is a residential suburb and housing estate in the northern part of Basingstoke, Hampshire, England.
-
D.
Warminster
Warminster is a market town in Wiltshire, England, known for its historic architecture, surrounding countryside, and role as a local transport and service hub.
-
E.
Warminster
Warminster is a suburban township in Bucks County, Pennsylvania, known for its residential communities, local commerce, and small general-aviation airport.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a3a24881908d81d634622fbbcc |
completed | April 14, 2026, 11:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7c71a43908190bc7537f0a2379599 |
completed | May 3, 2026, 10:07 p.m. |
Created at: April 9, 2026, 10:15 p.m.