Triple
T16302612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lexus NX |
E395827
|
entity |
| Predicate | competitor |
P1375
|
FINISHED |
| Object | Acura RDX |
E404410
|
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: Acura RDX | Statement: [Lexus NX, competitor, Acura RDX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Acura RDX Context triple: [Lexus NX, competitor, Acura RDX]
-
A.
Acura RDX
chosen
The Acura RDX is a compact luxury crossover SUV known for its blend of performance, comfort, and advanced technology features.
-
B.
Acura MDX
The Acura MDX is a midsize luxury crossover SUV known for its three-row seating, refined ride, and upscale features.
-
C.
Acura TLX
The Acura TLX is a midsize luxury sport sedan known for blending performance-oriented driving dynamics with advanced technology and premium comfort features.
-
D.
Acura ZDX
The Acura ZDX is a mid-size luxury crossover SUV known for its distinctive coupe-like styling and premium features, produced by Honda’s Acura division.
-
E.
Acura ILX
The Acura ILX is a compact luxury sedan from Honda’s premium brand, positioned as an entry-level model offering upscale features and sporty styling.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e3404288190a7106d62c15c3193 |
completed | April 17, 2026, 4:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a006798cf488190a68cf7e57902924e |
completed | May 10, 2026, 11:10 a.m. |
Created at: April 10, 2026, 5:06 a.m.