Triple
T4045985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota Land Cruiser |
E84066
|
entity |
| Predicate | hasGeneration |
P455
|
FINISHED |
| Object |
J90
The J90 is a generation of the Toyota Land Cruiser Prado mid-size SUV produced in the late 1990s and early 2000s, known for its off-road capability and body-on-frame construction.
|
E408505
|
NE FINISHED |
How this triple was built (4 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: J90 | Statement: [Toyota Land Cruiser, hasGeneration, J90]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: J90 Context triple: [Toyota Land Cruiser, hasGeneration, J90]
-
A.
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.
-
B.
J100
J100 is the internal model code used by Lexus to designate the second generation of its full-size luxury SUV, the Lexus LX.
-
C.
J7
J7 is a numbered junction on the M60 motorway in Greater Manchester, England, serving as an access point between the motorway and the surrounding local road network.
-
D.
J300
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.
-
E.
C90
C90 is the informal name for the 1990 standardization of the C programming language defined by ISO/IEC 9899.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: J90 Triple: [Toyota Land Cruiser, hasGeneration, J90]
Generated description
The J90 is a generation of the Toyota Land Cruiser Prado mid-size SUV produced in the late 1990s and early 2000s, known for its off-road capability and body-on-frame construction.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: J90 Target entity description: The J90 is a generation of the Toyota Land Cruiser Prado mid-size SUV produced in the late 1990s and early 2000s, known for its off-road capability and body-on-frame construction.
-
A.
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.
-
B.
J100
J100 is the internal model code used by Lexus to designate the second generation of its full-size luxury SUV, the Lexus LX.
-
C.
J7
J7 is a numbered junction on the M60 motorway in Greater Manchester, England, serving as an access point between the motorway and the surrounding local road network.
-
D.
J300
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.
-
E.
C90
C90 is the informal name for the 1990 standardization of the C programming language defined by ISO/IEC 9899.
- F. None of above. chosen
Provenance (5 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. |
| NEDg | Description generation | batch_69b556fec4708190b221893ec35f1a38 |
completed | March 14, 2026, 12:39 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69b557f73cbc8190b904089ab0fa97d6 |
completed | March 14, 2026, 12:43 p.m. |
Created at: March 9, 2026, 3:37 p.m.