Triple
T37485609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hall-effect thrusters |
E931521
|
entity |
| Predicate | hasTypicalThrust |
P161169
|
FINISHED |
| Object | millinewton to newton range |
—
|
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: millinewton to newton range | Statement: [Hall-effect thrusters, hasTypicalThrust, millinewton to newton range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalThrust Context triple: [Hall-effect thrusters, hasTypicalThrust, millinewton to newton range]
-
A.
providesThrustWith
Indicates that one entity generates and delivers propulsive force using or through another entity.
-
B.
thrustType
Indicates the type or method of thrust or propulsion used in performing an action or driving a system.
-
C.
thrustCapability
chosen
Indicates the level or capacity of force an entity can exert to propel or push something, typically in a specified direction or context.
-
D.
totalThrust
Indicates the combined amount of thrust produced by one or more propulsion sources acting on an object or system.
-
E.
thrustPerEngine
Indicates the amount of thrust produced by each individual engine in a multi-engine 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_69f76ec382248190b47844df596123c6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffe12ee59c8190bc7da386e6d5332d |
completed | May 10, 2026, 1:36 a.m. |
| PD | Predicate disambiguation | batch_69ffe0a138bc8190a3d4b48cd579e985 |
completed | May 10, 2026, 1:34 a.m. |
Created at: May 3, 2026, 4:17 p.m.