Triple

T9824520
Position Surface form Disambiguated ID Type / Status
Subject A338 road E238619 entity
Predicate connectsTo P845 FINISHED
Object A4 road E69163 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: A4 road | Statement: [A338 road, connectsTo, A4 road]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: A4 road
Context triple: [A338 road, connectsTo, A4 road]
  • A. A4 road chosen
    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.
  • B. A5 road
    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.
  • C. A5 road
    The A5 road is a primary route on the Isle of Man that connects the capital, Douglas, with the southern town of Port Erin, passing through several parishes including Malew.
  • D. A5 road
    The A5 road is a major route in Northern Ireland that connects the town of Omagh with other key destinations, serving as an important corridor for regional travel and transport.
  • 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_69ca84e0dd1881909800765d1e21f735 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb3181c688190afea3b27ee392a30 completed April 2, 2026, 12:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69f08ec96fe88190b791e6f50f39173f completed April 28, 2026, 10:41 a.m.
Created at: March 30, 2026, 8:31 p.m.