Triple
T20414613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intrepid-class starship |
E500674
|
entity |
| Predicate | warpNacelleType |
P24153
|
FINISHED |
| Object | variable-geometry nacelles |
—
|
LITERAL 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: variable-geometry nacelles | Statement: [Intrepid-class starship, warpNacelleType, variable-geometry nacelles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warpNacelleType Context triple: [Intrepid-class starship, warpNacelleType, variable-geometry nacelles]
-
A.
naveType
Indicates the architectural or structural type or style of a building’s nave in relation to that nave.
-
B.
propulsionFeature
chosen
Indicates a relationship where a propulsion-related characteristic or capability is attributed to an entity.
-
C.
fuselageType
Indicates the specific structural or design category of an aircraft’s fuselage that an entity belongs to or uses.
-
D.
nuclearWarheadCarrier
Indicates that an entity is designed or used to carry, transport, or deliver nuclear warheads.
-
E.
plannedPropulsionType
Indicates the type of propulsion system that is intended or scheduled to be used for an object or vehicle.
- F. None of above.
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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67a4281048190a2b016ec16b7d203 |
completed | April 20, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:30 a.m.