Triple

T16067761
Position Surface form Disambiguated ID Type / Status
Subject Toyota Motor Manufacturing UK E389774 entity
Predicate hasAbbreviation P43 FINISHED
Object TMUK E137834 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: TMUK | Statement: [Toyota Motor Manufacturing UK, hasAbbreviation, TMUK]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TMUK
Context triple: [Toyota Motor Manufacturing UK, hasAbbreviation, TMUK]
  • A. TMUK chosen
    TMUK is Toyota's United Kingdom-based automobile manufacturing subsidiary, operating major production plants such as those in Burnaston and Deeside.
  • B. TUK
    TUK is the abbreviation for the Technical University of Kaiserslautern, a German public research university known for its strong engineering and science programs.
  • C. TUKE
    TUKE is a major Slovak technical university based in Košice, known for its engineering, technology, and applied science programs.
  • D. TMK
    TMK is the abbreviation for the Kosovo Protection Corps, a civil emergency and disaster response organization that succeeded the Kosovo Liberation Army after the Kosovo War.
  • E. DMU
    DMU is the IATA airport code for Dimapur Airport, which serves the city of Dimapur in the Indian state of Nagaland.
  • 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_69d86daf32ec8190a8c0466c8f49c3c0 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e183baf29481908e5c66879e125363 completed April 17, 2026, 12:50 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffe480d59c8190962ac596a872b5e0 completed May 10, 2026, 1:50 a.m.
Created at: April 10, 2026, 4:57 a.m.