Triple

T13228138
Position Surface form Disambiguated ID Type / Status
Subject Jaguar XE E314933 entity
Predicate competitor P1375 FINISHED
Object Lexus IS E327256 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: Lexus IS | Statement: [Jaguar XE, competitor, Lexus IS]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lexus IS
Context triple: [Jaguar XE, competitor, Lexus IS]
  • A. Lexus IS chosen
    The Lexus IS is a compact luxury sports sedan from Toyota’s premium brand, known for its refined ride, upscale interior, and strong reliability.
  • B. Lexus ES
    The Lexus ES is a midsize luxury sedan known for its comfort, refinement, and reliability, positioned as a premium yet value-oriented alternative to German executive cars.
  • C. Lexus GS
    The Lexus GS is a mid-size luxury sedan known for blending refined comfort, strong performance, and advanced technology within Lexus’s premium lineup.
  • D. Lexus LS
    The Lexus LS is a flagship full-size luxury sedan from Toyota’s Lexus brand, known for its refinement, comfort, and reliability.
  • E. Lexus RX
    The Lexus RX is a mid-size luxury crossover SUV known for its refined ride, upscale interior, and strong reputation for reliability.
  • 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_69d806affc688190a25b6ccc588e9c72 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98d3232d48190a3c792b025c596a6 completed April 10, 2026, 11:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6ff2a4b0c8190a853a1f6f4d1cbaf completed May 3, 2026, 7:54 a.m.
Created at: April 9, 2026, 9:21 p.m.