Triple
T4550479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loughor estuary |
E110149
|
entity |
| Predicate | hasNearbyVillage |
P4647
|
FINISHED |
| Object | Gowerton |
E401988
|
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: Gowerton | Statement: [Loughor estuary, hasNearbyVillage, Gowerton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gowerton Context triple: [Loughor estuary, hasNearbyVillage, Gowerton]
-
A.
Gowerton
chosen
Gowerton is a suburban village in South Wales, known as a commuter settlement northwest of Swansea with a mix of residential areas and local amenities.
-
B.
Owerton
Owerton is an alternative spelling of the name Overton, which is used for various places and surnames in English-speaking regions.
-
C.
Gower
Gower is a UK parliamentary constituency in South Wales, named after the Gower Peninsula and represented in the House of Commons.
-
D.
Golborne
Golborne is a town in the Metropolitan Borough of Wigan in Greater Manchester, England, historically part of Lancashire.
-
E.
Coryton
Coryton is a suburban area and railway terminus in Cardiff, Wales, served by local commuter trains.
- 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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57f5a0a081909977ccbb8aba633c |
completed | March 20, 2026, 2:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bdb94cab408190956ef333aa810a3b |
completed | March 20, 2026, 9:17 p.m. |
Created at: March 20, 2026, 1:05 p.m.