Triple
T4518824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sukhoi Superjet 100 |
E103215
|
entity |
| Predicate | rangeVariant |
P57186
|
FINISHED |
| Object | SSJ100-95 |
E448636
|
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: SSJ100-95 | Statement: [Sukhoi Superjet 100, rangeVariant, SSJ100-95]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SSJ100-95 Context triple: [Sukhoi Superjet 100, rangeVariant, SSJ100-95]
-
A.
SSJ100
chosen
SSJ100 is a Russian regional jet airliner developed by Sukhoi Civil Aircraft for short- to medium-haul passenger service.
-
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.
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.
-
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.
J-Air
J-Air is a Japanese regional airline operating domestic feeder and short-haul routes on behalf of Japan Airlines.
- 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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd6231856c8190be9386a0ae15e7cf |
completed | March 20, 2026, 3:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bdacd174c88190a186bc2ecc20fcd5 |
completed | March 20, 2026, 8:23 p.m. |
Created at: March 20, 2026, 1:02 p.m.