Triple

T9199594
Position Surface form Disambiguated ID Type / Status
Subject Cambridge inner ring road E220802 entity
Predicate connectsWith P37 FINISHED
Object A1303 E533303 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: A1303 | Statement: [Cambridge inner ring road, connectsWith, A1303]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: A1303
Context triple: [Cambridge inner ring road, connectsWith, A1303]
  • A. A1303 chosen
    The A1303 is a primary road in Cambridge, England, forming part of an important east–west route through the city and its surrounding area.
  • B. A130
    The A130 is a major road in Essex, England, linking towns such as Basildon with other key routes in the regional highway network.
  • C. A13
    A13 is a major Swiss motorway running along the country’s eastern side, providing an important north–south transit route through the Alps.
  • D. A13
    A13 is a major road in England that serves as a key route linking London with areas in south Essex, including Basildon.
  • E. A134
    The A134 is a primary road in eastern England that connects several towns and rural areas, including passing through the village of Stoke Ferry in Norfolk.
  • 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_69ca83e8e9248190862cf3e41693b310 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccd881c5d48190bbc33fac71a1d849 completed April 1, 2026, 8:34 a.m.
NED1 Entity disambiguation (via context triple) batch_69d05c40267c8190926f4d5c912d0f45 completed April 4, 2026, 12:33 a.m.
Created at: March 30, 2026, 7:25 p.m.