Triple

T14931538
Position Surface form Disambiguated ID Type / Status
Subject European route E12 E372276 entity
Predicate hasRouteNumber P1864 FINISHED
Object E12 E911278 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: E12 | Statement: [European route E12, hasRouteNumber, E12]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: E12
Context triple: [European route E12, hasRouteNumber, E12]
  • A. E12 chosen
    E12 is a European route that forms part of the international E-road network, connecting Finland with Sweden and Norway across the Nordic region.
  • B. E21
    E21 is the internal designation for the first generation of the BMW 3 Series compact executive car, produced in the 1970s and early 1980s.
  • C. E22
    E22 is a major European route that forms part of the international E-road network, linking multiple countries across Europe.
  • D. E10
    E10 is the internal BMW chassis code for the classic 02 Series compact sports sedans produced in the late 1960s and 1970s.
  • E. E10
    E10 is a European route that runs from Å in Norway to Luleå in Sweden, crossing the Lofoten Islands and providing a key road link in northern Scandinavia.
  • 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_69d85cc9da0c81908d583ca3f63a3908 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded64550dc8190ba44120df00ba498 completed April 15, 2026, 12:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe72c86b5c81909e601a3fc78276bd completed May 8, 2026, 11:33 p.m.
Created at: April 10, 2026, 2:36 a.m.