Triple
T32912547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zefram Cochrane |
E841918
|
entity |
| Predicate | warpDriveFeature |
P24153
|
FINISHED |
| Object | warp 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: warp nacelles | Statement: [Zefram Cochrane, warpDriveFeature, warp nacelles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warpDriveFeature Context triple: [Zefram Cochrane, warpDriveFeature, warp nacelles]
-
A.
warpDrivePioneer
Indicates that an entity is recognized as having been among the first to develop, invent, or successfully use warp drive technology.
-
B.
propulsionFeature
chosen
Indicates a relationship where a propulsion-related characteristic or capability is attributed to an entity.
-
C.
maximumWarpSpeed
Indicates the highest warp speed that an entity (such as a spacecraft) is capable of achieving or operating at.
-
D.
hyperdrive
Indicates that an entity is capable of or engaged in faster-than-light travel using a hyperdrive propulsion system.
-
E.
hasWarp
Indicates that one entity possesses, is equipped with, or is capable of using a warp or warp-related mechanism in relation to another entity or context.
- 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:19 a.m.