Triple

T7908660
Position Surface form Disambiguated ID Type / Status
Subject European route E80 E183642 entity
Predicate routeNumber P1864 FINISHED
Object E80 E178612 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: E80 | Statement: [European route E80, routeNumber, E80]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: E80
Context triple: [European route E80, routeNumber, E80]
  • A. E80 chosen
    E80 is a major European route that forms part of the international road network connecting Podgorica with other key cities across the continent.
  • B. E89
    E89 is the internal BMW designation for the second-generation Z4 roadster, known for its retractable hardtop and sporty grand-touring character.
  • C. EH8
    EH8 is a central Edinburgh postcode district covering areas including Holyrood and parts of the city’s historic core.
  • D. J80
    J80 is the internal chassis code used by Toyota for the 80-series Land Cruiser platform that underpins the first-generation Lexus LX luxury SUV.
  • E. 190E
    The Mercedes-Benz 190E is a compact executive sedan from the 1980s and early 1990s, renowned for its advanced engineering, build quality, and motorsport-bred performance variants like the 190E 2.3-16 and 2.5-16.
  • 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_69ca828dec0c81908b8f55a4dbbb53ff completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3a5c85ac81908de2ca387826ea2f completed March 31, 2026, 3:07 a.m.
NED1 Entity disambiguation (via context triple) batch_69cb5bd0024c81909679a45612bcb1a7 completed March 31, 2026, 5:29 a.m.
Created at: March 30, 2026, 5:03 p.m.