Triple

T5948435
Position Surface form Disambiguated ID Type / Status
Subject Ronaldsway E132335 entity
Predicate hasRoadConnection P385 FINISHED
Object A5 road E295818 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: A5 road | Statement: [Ronaldsway, hasRoadConnection, A5 road]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: A5 road
Context triple: [Ronaldsway, hasRoadConnection, A5 road]
  • A. A5 road chosen
    The A5 road is a major historic route in Great Britain running from London to Holyhead, forming part of the key connection between England and Wales.
  • B. A4 road
    The A4 road is a major historic route in England that runs west from central London through key cities such as Reading, Bath, and Bristol toward Avonmouth.
  • C. A50 road
    The A50 road is a major east–west trunk route in England linking Warrington in Cheshire to Leicester in Leicestershire, passing through the Stoke-on-Trent area.
  • D. A52 road
    The A52 road is a major east–west route in England that runs across the East Midlands, linking cities such as Nottingham and Derby with coastal towns like Skegness.
  • E. A2 road
    The A2 road is a major route in southeast England connecting London to the port of Dover and forming part of a key corridor to mainland Europe.
  • 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_69c00869d3308190af89b2453e0f7546 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c0397deea08190b9397d0413740300 completed March 22, 2026, 6:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69d0b12e42e48190b62b772d150117f2 completed April 4, 2026, 6:35 a.m.
Created at: March 22, 2026, 4:01 p.m.