Triple

T10615636
Position Surface form Disambiguated ID Type / Status
Subject Autoroute A62 E276111 entity
Predicate roadNumber P1864 FINISHED
Object A62 E697279 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: A62 | Statement: [Autoroute A62, roadNumber, A62]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: A62
Context triple: [Autoroute A62, roadNumber, A62]
  • A. A62 chosen
    A62 is a major A-road in northern England that connects the cities of Manchester and Leeds.
  • B. A66
    A66 is a major trans-Pennine road in northern England that connects the Lake District with the North East, serving as an important east–west transport route.
  • C. A682
    The A682 is a primary road in northern England that runs through Lancashire and North Yorkshire, linking towns such as Rawtenstall and serving as a key route across the Pennines.
  • D. A676
    The A676 is a road in North West England that passes through Edenfield and connects several towns in the Greater Manchester and Lancashire area.
  • E. A607
    A607 is a primary A-road in England that runs between Leicester and Grantham, serving as an important regional route through the East Midlands.
  • 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_69d6aaf948d88190806cc3a8c47a3fb2 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d6df6d76dc8190bd8d481fed3225d9 completed April 8, 2026, 11:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69d95ecd44b08190bccbedd63544ba17 completed April 10, 2026, 8:34 p.m.
Created at: April 8, 2026, 7:33 p.m.