Triple
T16548038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonymaen |
E401995
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Landore |
E401996
|
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: Landore | Statement: [Bonymaen, borders, Landore]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Landore Context triple: [Bonymaen, borders, Landore]
-
A.
Landore
chosen
Landore is a district of Swansea in South Wales, known historically for its industrial heritage and proximity to the River Tawe.
-
B.
Montgarri
Montgarri is a small, remote mountain village and former monastery site in the Val d'Aran of the Catalan Pyrenees, known for its scenic alpine setting and pilgrimage church.
-
C.
Gronant
Gronant is a coastal village and community in Denbighshire, Wales, known for its sand dunes, nature reserve, and proximity to the seaside town of Prestatyn.
-
D.
Sandarne
Sandarne is a small locality in east-central Sweden, situated on the coast within Gävleborg County.
-
E.
Dynnyrne
Dynnyrne is a residential suburb of Hobart, Tasmania, situated on the city’s hilly southern fringe.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34fbf79048190b761008441762374 |
completed | April 18, 2026, 9:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0067b4f6448190812632ab9023b665 |
completed | May 10, 2026, 11:10 a.m. |
Created at: April 10, 2026, 5:15 a.m.