Triple
T13561472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volvo XC60 |
E323917
|
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: [Volvo XC60, competitor, Lexus NX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lexus NX Context triple: [Volvo XC60, 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaff5219081909cf60423e79d278f |
completed | April 12, 2026, 2:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f76bb1ef508190ab587bd2aa34795b |
completed | May 3, 2026, 3:37 p.m. |
Created at: April 9, 2026, 9:47 p.m.