Triple

T13476845
Position Surface form Disambiguated ID Type / Status
Subject Lexus RX E318271 entity
Predicate hasModelVariant P455 FINISHED
Object Lexus RX 330 E318271 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 RX 330 | Statement: [Lexus RX, hasModelVariant, Lexus RX 330]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lexus RX 330
Context triple: [Lexus RX, hasModelVariant, Lexus RX 330]
  • A. Lexus RX chosen
    The Lexus RX is a mid-size luxury crossover SUV known for its refined ride, upscale interior, and strong reputation for reliability.
  • B. Lexus RX/NX/GX
    The Lexus RX/NX/GX are Lexus’s popular luxury SUV lineup, spanning compact, midsize, and off-road-capable models known for comfort, refinement, and reliability.
  • 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 GX
    The Lexus GX is a mid-size luxury SUV known for its body-on-frame construction, off-road capability, and upscale interior.
  • E. Lexus IS
    The Lexus IS is a compact luxury sports sedan from Toyota’s premium brand, known for its refined ride, upscale interior, and strong 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_69d806b6bfec819089222715b2e86c8e completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaf2551b48190a074fd256791742d completed April 12, 2026, 2:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69f75d8ab8548190a0a1adbe927c95d0 completed May 3, 2026, 2:36 p.m.
Created at: April 9, 2026, 9:42 p.m.