Triple
T6194080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wrexham County Borough |
E138466
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Ruabon |
E152082
|
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: Ruabon | Statement: [Wrexham County Borough, hasSettlement, Ruabon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ruabon Context triple: [Wrexham County Borough, hasSettlement, Ruabon]
-
A.
Ruabon
chosen
Ruabon is a village and community in Wrexham County Borough, Wales, historically known for its coal mining and brickmaking industries and its location on key transport routes.
-
B.
Rhun
Rhûn is an eastern region of J.R.R. Tolkien’s Middle-earth, largely unexplored in the stories and home to various distant and often hostile peoples.
-
C.
Waunarlwydd
Waunarlwydd is a suburban village and community on the western edge of Swansea in South Wales, known for its residential character and local amenities.
-
D.
Talyllyn
Talyllyn is a historic narrow-gauge steam locomotive that operates on the Talyllyn Railway in Wales.
-
E.
Bonymaen
Bonymaen is a residential district and community in the east of Swansea, Wales.
- 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_69c008ab9b3081908a11b2c744838435 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062431ae88190a1bf6ca91f3dc690 |
completed | March 22, 2026, 9:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c16f1c162081909cf34e827f1bd7d7 |
completed | March 23, 2026, 4:49 p.m. |
Created at: March 22, 2026, 4:19 p.m.