Triple

T16643778
Position Surface form Disambiguated ID Type / Status
Subject Acura RDX E404410 entity
Predicate competitor P1375 FINISHED
Object Lexus NX E395827 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 NX | Statement: [Acura RDX, competitor, Lexus NX]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lexus NX
Context triple: [Acura RDX, competitor, Lexus NX]
  • A. Lexus NX chosen
    The Lexus NX is a compact luxury crossover SUV known for its upscale interior, advanced technology features, and refined ride.
  • B. Lexus RX
    The Lexus RX is a mid-size luxury crossover SUV known for its refined ride, upscale interior, and strong reputation for reliability.
  • C. Lexus UX
    The Lexus UX is a subcompact luxury crossover SUV known for its upscale interior, advanced safety features, and efficient hybrid powertrain options.
  • D. Lexus HS
    The Lexus HS is a compact luxury hybrid sedan that was Lexus’s first dedicated hybrid model, offering fuel-efficient performance and premium comfort features.
  • E. 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.
  • 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_69d8838a41f08190b0c3f79c47df5078 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e37ad3b12c8190a32e33d9ecff9dae completed April 18, 2026, 12:36 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0084bd1b648190b6189533dcd7b9ac completed May 10, 2026, 1:14 p.m.
Created at: April 10, 2026, 5:18 a.m.