Triple

T22513565
Position Surface form Disambiguated ID Type / Status
Subject Lanesborough E556583 entity
Predicate connectedByRoad P11435 FINISHED
Object R371 road NE NERFINISHED

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: R371 road | Statement: [Lanesborough, connectedByRoad, R371 road]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: R371 road
Context triple: [Lanesborough, connectedByRoad, R371 road]
  • A. R371 road chosen
    The R371 road is a regional route in Ireland that connects the village of Roosky in County Roscommon with nearby towns and the wider regional road network.
  • B. R301 road
    The R301 road is a regional route in South Africa’s Western Cape that connects several towns in the Cape Winelands region.
  • C. R741 road
    The R741 road is a regional route in County Wexford, Ireland, connecting several towns and villages inland with the coastal area near Wexford town.
  • D. R736 road
    The R736 road is a regional route in County Wexford, Ireland, connecting several local towns and coastal areas to the wider road network.
  • E. R27 road
    The R27 road is a regional route in South Africa that runs along the west coast, linking Cape Town with towns in the Western and Northern Cape.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e555edc81909ca803587dafd747 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15d62bea48190aaf34aa93bb3f67b completed April 29, 2026, 1:22 a.m.
Created at: April 16, 2026, 8:50 p.m.