Triple
T4045990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota Land Cruiser |
E84066
|
entity |
| Predicate | hasGeneration |
P455
|
FINISHED |
| Object | J300 |
E250086
|
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: J300 | Statement: [Toyota Land Cruiser, hasGeneration, J300]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: J300 Context triple: [Toyota Land Cruiser, hasGeneration, J300]
-
A.
J300
chosen
J300 is the internal model code for the fourth-generation Lexus LX, a full-size luxury SUV built on Toyota’s latest Land Cruiser platform.
-
B.
J200
J200 is the internal chassis code designating the third-generation Lexus LX full-size luxury SUV.
-
C.
GJ-3
GJ-3 is the regional vehicle registration code assigned to the city of Rajkot in the Indian state of Gujarat.
-
D.
J80
J80 is the internal chassis code used by Toyota for the 80-series Land Cruiser platform that underpins the first-generation Lexus LX luxury SUV.
-
E.
J100
J100 is the internal model code used by Lexus to designate the second generation of its full-size luxury SUV, the Lexus LX.
- 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_69aed930bd5c819083e7dcc14fc44f69 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb6135b481909d2be890a2140ff9 |
completed | March 9, 2026, 4:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b55652228c8190a9f301676deb0055 |
completed | March 14, 2026, 12:36 p.m. |
Created at: March 9, 2026, 3:37 p.m.