Triple
T10594984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J300 |
E250086
|
entity |
| Predicate | marketedAs |
P1395
|
FINISHED |
| Object | Lexus LX 600 |
E50659
|
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 LX 600 | Statement: [J300, marketedAs, Lexus LX 600]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lexus LX 600 Context triple: [J300, marketedAs, Lexus LX 600]
-
A.
Lexus LX
chosen
The Lexus LX is a full-size luxury SUV known for its off-road capability, premium features, and close relation to the Toyota Land Cruiser.
-
B.
Lexus GX
The Lexus GX is a mid-size luxury SUV known for its body-on-frame construction, off-road capability, and upscale interior.
-
C.
Infiniti QX80
The Infiniti QX80 is a full-size luxury SUV known for its powerful V8 engine, upscale interior, and three-row seating aimed at families seeking comfort and towing capability.
-
D.
Infiniti QX60
The Infiniti QX60 is a midsize luxury crossover SUV known for its three-row seating, upscale features, and family-oriented comfort.
-
E.
Lexus LS
The Lexus LS is a flagship full-size luxury sedan from Toyota’s Lexus brand, known for its refinement, comfort, 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5278cbf9081909ef419b0144d5019 |
completed | April 7, 2026, 3:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69dff76eef4c8190b4fe681a9431207d |
completed | April 15, 2026, 8:39 p.m. |
Created at: April 6, 2026, 12:41 p.m.