Triple
T31957749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S48 |
E815952
|
entity |
| Predicate | associatedWithPropulsion |
P24153
|
FINISHED |
| Object | nuclear propulsion |
—
|
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: nuclear propulsion | Statement: [S48, associatedWithPropulsion, nuclear propulsion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithPropulsion Context triple: [S48, associatedWithPropulsion, nuclear propulsion]
-
A.
originalPropulsion
Indicates that one entity serves as the initial or native means of propulsion or movement for another entity.
-
B.
propulsionFeature
chosen
Indicates a relationship where a propulsion-related characteristic or capability is attributed to an entity.
-
C.
hasPropulsionComponent
Indicates that an entity includes or is equipped with a component responsible for providing propulsion.
-
D.
associatedWithEngine
Indicates a relationship in which something is connected, linked, or related to an engine, typically through use, function, or dependency.
-
E.
appliesToPropulsionType
Indicates that something is relevant or specifically applicable to a particular type of propulsion system.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:08 a.m.