Triple
T33211727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titan IIIB |
E850180
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Titan III family member |
C59767
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Titan III family member Context triple: [Titan IIIB, instanceOf, Titan III family member]
-
A.
Turbostar family
The Turbostar family is a series of regional diesel multiple unit trains designed for short- to medium-distance passenger services, known for their modular construction and widespread use in the UK rail network.
-
B.
MiG-29 derivative
A MiG-29 derivative is any aircraft design or variant that evolves from the original MiG-29 Fulcrum platform, incorporating modifications in structure, avionics, propulsion, or mission role while retaining its core aerodynamic and design lineage.
-
C.
Generation III+ reactor
A Generation III+ reactor is an advanced nuclear power plant design that enhances Generation III features with improved safety systems, higher efficiency, and longer operational lifetimes, often incorporating passive safety and standardized modular construction.
-
D.
Terminator model
A Terminator model is a highly advanced, human-like robotic assassin designed for infiltration, combat, and execution of specific targets, often featuring adaptive AI and durable endoskeletal construction.
-
E.
Kilo-class variant
A Kilo-class variant is a modified version of the Russian-designed Kilo-class diesel-electric attack submarine, incorporating specific upgrades or alterations in systems, capabilities, or configuration for particular operators or missions.
- F. None of above. chosen
Provenance (1 batch)
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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:30 a.m.