Triple
T8929426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Audi A8 |
E212613
|
entity |
| Predicate | competitor |
P1375
|
FINISHED |
| Object | Lexus LS |
E321621
|
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 LS | Statement: [Audi A8, competitor, Lexus LS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lexus LS Context triple: [Audi A8, competitor, Lexus LS]
-
A.
Lexus LS
chosen
The Lexus LS is a flagship full-size luxury sedan from Toyota’s Lexus brand, known for its refinement, comfort, and 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 LC
The Lexus LC is a luxury grand tourer coupe (and convertible) known for its striking design, refined performance, and high-end craftsmanship within Lexus’s flagship lineup.
-
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_69ca8395c438819087d7cb844ab5990c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc667470308190a75ba63de803e3a2 |
completed | April 1, 2026, 12:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfba5e887c8190851f2fb533653c6e |
completed | April 3, 2026, 1:02 p.m. |
Created at: March 30, 2026, 6:57 p.m.