Triple
T32912546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zefram Cochrane |
E841918
|
entity |
| Predicate | warpDrivePowerSource |
P171553
|
FINISHED |
| Object | matter-antimatter reactor |
—
|
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: matter-antimatter reactor | Statement: [Zefram Cochrane, warpDrivePowerSource, matter-antimatter reactor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warpDrivePowerSource Context triple: [Zefram Cochrane, warpDrivePowerSource, matter-antimatter reactor]
-
A.
warpDrivePioneer
Indicates that an entity is recognized as having been among the first to develop, invent, or successfully use warp drive technology.
-
B.
propulsionReactorType
chosen
Indicates the type or kind of reactor used as the primary source of propulsion.
-
C.
propulsionSource
Indicates the mechanism or system that provides thrust or driving force for an object’s movement.
-
D.
derivesPowerFrom
Indicates that one entity obtains or is granted its power, authority, or energy as a result of another entity.
-
E.
propulsionModule
Indicates a relationship where an entity functions as, or is equipped with, a module responsible for providing propulsion.
- 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_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:19 a.m.