Triple

T17943253
Position Surface form Disambiguated ID Type / Status
Subject SSJ100 E448636 entity
Predicate hasVariant P455 FINISHED
Object SSJ100LR NE NERFINISHED

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: SSJ100LR | Statement: [SSJ100, hasVariant, SSJ100LR]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SSJ100LR
Context triple: [SSJ100, hasVariant, SSJ100LR]
  • A. SSJ100 chosen
    SSJ100 is a Russian regional jet airliner developed by Sukhoi Civil Aircraft for short- to medium-haul passenger service.
  • B. Super Cub C100
    The Super Cub C100 is Honda’s iconic small-displacement motorcycle introduced in 1958, renowned for its step-through design, reliability, and role in popularizing affordable motorized transport worldwide.
  • C. SSJ
    SSJ is the IATA airport code for Sandnessjøen Airport, a regional airport serving the town of Sandnessjøen in Nordland, Norway.
  • D. Flying J
    Flying J is a chain of highway travel centers and truck stops in North America, known for providing fuel, food, and amenities for professional drivers and motorists.
  • 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 (2 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_69d8b9f79d14819095540856928f0e25 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4ad97611c8190a861467ae51f6c48 completed April 19, 2026, 10:25 a.m.
Created at: April 10, 2026, 10:21 a.m.