Triple
T7192838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lexus |
E167735
|
entity |
| Predicate | hasModel |
P2390
|
FINISHED |
| Object | Lexus IS |
E327256
|
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 IS | Statement: [Lexus, hasModel, Lexus IS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lexus IS Context triple: [Lexus, hasModel, Lexus IS]
-
A.
Lexus IS
chosen
The Lexus IS is a compact luxury sports sedan from Toyota’s premium brand, known for its refined ride, upscale interior, and strong 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 LS
The Lexus LS is a flagship full-size luxury sedan from Toyota’s Lexus brand, known for its refinement, comfort, and reliability.
-
D.
Lexus RX
The Lexus RX is a mid-size luxury crossover SUV known for its refined ride, upscale interior, and strong reputation for reliability.
-
E.
Lexus RC
The Lexus RC is a compact luxury sports coupe known for its refined styling, high-quality interior, and available high-performance variants.
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e9036544819083c70a5d2135ba4b |
completed | March 27, 2026, 8:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7d37f67bc8190bc11ab16f7cbe909 |
completed | March 28, 2026, 1:11 p.m. |
Created at: March 27, 2026, 2:50 p.m.