Triple

T19531216
Position Surface form Disambiguated ID Type / Status
Subject E22 European route E488655 entity
Predicate roadNumber P1864 FINISHED
Object E22 NE NERFINISHED

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: E22 | Statement: [E22 European route, roadNumber, E22]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: E22
Context triple: [E22 European route, roadNumber, E22]
  • A. E22 chosen
    E22 is a major European route that forms part of the international E-road network, linking multiple countries across Europe.
  • 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. E2
    E2 is a designated expressway route number within the STAR Tollway system in the Philippines.
  • D. E 220 d
    The E 220 d is a diesel-powered variant of the Mercedes-Benz E-Class executive sedan, known for its balance of efficiency, comfort, and refined performance.
  • E. E20
    E20 is a major trans-European route running west–east across several countries from Ireland through the United Kingdom and northern Europe to Russia.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8db5b6c8190984b61f91981f575 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6363fd1f8819080805346efad2579 completed April 20, 2026, 2:20 p.m.
Created at: April 10, 2026, 1:41 p.m.