Triple
T5214637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Enterprise (NCC-1701-A) |
E117721
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Constitution-class starship |
C17830
|
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: Constitution-class starship Context triple: [USS Enterprise (NCC-1701-A), instanceOf, Constitution-class starship]
-
A.
Tribal-class destroyer
The Tribal-class destroyer was a class of large, fast, and heavily armed destroyers built for the Royal Navy and other Commonwealth navies in the late 1930s, designed to provide powerful fleet screening and offensive capabilities during World War II.
-
B.
battlecruiser class
A battlecruiser class represents a large, fast, heavily armed warship optimized for long-range offensive power at the expense of some armor protection compared to battleships.
-
C.
Corellian YT-1300 light freighter
A Corellian YT-1300 light freighter is a highly customizable, durable, and fast starship primarily used for cargo transport but often modified for smuggling, combat, and independent operations across the galaxy.
-
D.
Bagley-class destroyer
A Bagley-class destroyer is a type of U.S. Navy warship built in the late 1930s, characterized by high speed, heavy torpedo armament, and service in World War II as an escort and attack vessel.
-
E.
Leander-class light cruiser
The Leander-class light cruiser was a group of British Royal Navy warships built in the 1930s, designed as fast, versatile cruisers for trade protection, fleet screening, and colonial patrol duties.
- 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_69bd4464ba3c8190bc16b2ebbe42ddb0 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:47 p.m.