Triple
T22085877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orville-class exploratory vessel |
E545774
|
entity |
| Predicate | fasterThanLightCapability |
P24153
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Orville-class exploratory vessel, fasterThanLightCapability, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fasterThanLightCapability Context triple: [Orville-class exploratory vessel, fasterThanLightCapability, true]
-
A.
warpDrivePioneer
Indicates that an entity is recognized as having been among the first to develop, invent, or successfully use warp drive technology.
-
B.
supercruiseCapability
Indicates that an entity possesses the ability to sustain high-speed travel (typically supersonic) without using afterburners or additional boost mechanisms.
-
C.
hasStarship
Indicates that one entity possesses, controls, or is associated with a particular starship.
-
D.
propulsionFeature
chosen
Indicates a relationship where a propulsion-related characteristic or capability is attributed to an entity.
-
E.
hasForceCarrier
Indicates that a fundamental interaction or force is mediated or carried by a specific particle or field.
- 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_69e11e3523488190badd54b5d580c00d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128ba24ac819082fc4aa274553481 |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:29 p.m.